Configuration for EC2 instance autostartup
-
I'll add my voice... I'm lost.
-
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
-
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
-
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
I know. Powering on should be a simple API call from another computer that's currently powered on. Might take some scripting , but shouldn't be super difficult.
-
@travisdh1 said in Configuration for EC2 instance autostartup:
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
I know. Powering on should be a simple API call from another computer that's currently powered on. Might take some scripting , but shouldn't be super difficult.
Should be done via the Amazon API, how would another computer do it?
-
@scottalanmiller said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
I know. Powering on should be a simple API call from another computer that's currently powered on. Might take some scripting , but shouldn't be super difficult.
Should be done via the Amazon API, how would another computer do it?
OP sounded like they don't want a human to have to push a button, requires a computer that's running to make the API call.
-
@travisdh1 said in Configuration for EC2 instance autostartup:
@scottalanmiller said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
I know. Powering on should be a simple API call from another computer that's currently powered on. Might take some scripting , but shouldn't be super difficult.
Should be done via the Amazon API, how would another computer do it?
OP sounded like they don't want a human to have to push a button, requires a computer that's running to make the API call.
Yes, but an API call to Amazon. Not like WoL.
-
@scottalanmiller said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@scottalanmiller said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
I know. Powering on should be a simple API call from another computer that's currently powered on. Might take some scripting , but shouldn't be super difficult.
Should be done via the Amazon API, how would another computer do it?
OP sounded like they don't want a human to have to push a button, requires a computer that's running to make the API call.
Yes, but an API call to Amazon. Not like WoL.
Sorry, another device. Would that be proper terminology?
-
May be he is looking for something like https://aws.amazon.com/answers/infrastructure-management/ec2-scheduler/
-
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Ya here's a sample:
--- - name: create aws instances hosts: localhost tasks: - name: create ec2 instance ec2: key_name: centos instance_type: t2.micro image: ami-ae7bfdb8 wait: yes group: dns count: 1 instance_tags: type: dns region: us-east-1 register: ec2 - name: wait for SSH wait_for: host: "{{ item.public_dns_name }}" port: 22 delay: 30 timeout: 320 state: started with_items: "{{ ec2.instances }}" -
@reid-cooper said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@jaredbusch said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@dashrender said in Configuration for EC2 instance autostartup:
The only thing I can figure is a) he wants to schedule a script or b) an instance will be powered off normally, but he wants it to come on at a specific time.
Which is weird. You pay even if it’s off. So just bring up instances when you need them.
Right I read a post the other day someplace where the OP was wanting to turn off Azure servers after hours. You still pay for those until they are destroyed.
But the OP in that thread mentioned something about some agreement you can get that you pay less for powered off servers.
I wonder what the use case is for that vs just bring them up when you need them?
Automatically creating/destroying cloud instances on an as-needed basis would be a great thing to automate, actually.
Creating and destroying is not turning on and off.
Right, turning on and off doesn't make much sense. Just create destroy as needed.
-
@ambarishrh said in Configuration for EC2 instance autostartup:
May be he is looking for something like https://aws.amazon.com/answers/infrastructure-management/ec2-scheduler/
I don't get that. It seems less flexible than an ELB and you would have to continually calculate what you would need. Why not just pay for the ELB and have it automatically do this?
If you really don't need this type of infrastructure, then just use something like Vultr or DO.
-
@stacksofplates said in Configuration for EC2 instance autostartup:
@ambarishrh said in Configuration for EC2 instance autostartup:
May be he is looking for something like https://aws.amazon.com/answers/infrastructure-management/ec2-scheduler/
I don't get that. It seems less flexible than an ELB and you would have to continually calculate what you would need. Why not just pay for the ELB and have it automatically do this?
If you really don't need this type of infrastructure, then just use something like Vultr or DO.
I'm gonna have to read up on the ELB. Looks like exactly the thing I've been wondering why nobody had.
-
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@ambarishrh said in Configuration for EC2 instance autostartup:
May be he is looking for something like https://aws.amazon.com/answers/infrastructure-management/ec2-scheduler/
I don't get that. It seems less flexible than an ELB and you would have to continually calculate what you would need. Why not just pay for the ELB and have it automatically do this?
If you really don't need this type of infrastructure, then just use something like Vultr or DO.
I'm gonna have to read up on the ELB. Looks like exactly the thing I've been wondering why nobody had.
Ya they're pretty awesome. You need to use their monitoring to get the most out of it, but if you are operating at that scale it's worth it anyway.
-
@stacksofplates
Hi, I need to configure every day the server need to be powered on automatically some time and the same need to be powered off in the evening. Power off i was done through scheduled task in windows. But powering on is the challenge. I tried with lambda option but having some error -
@sadee said in Configuration for EC2 instance autostartup:
@stacksofplates
Hi, I need to configure every day the server need to be powered on automatically some time and the same need to be powered off in the evening. Power off i was done through scheduled task in windows. But powering on is the challenge. I tried with lambda option but having some errorThis really just rephrasing the OP. What is this server doing?
-
It would make sense for an app running on another Amazon Virtual Machine as @travisdh1 particularly in telecom where you create and destroy servers on the fly to handle call bursts, or to just eliminate a dorked server that is having trouble.
Turning on and off though, probably he is after something else.
-
@stacksofplates said in Configuration for EC2 instance autostartup:
@travisdh1 said in Configuration for EC2 instance autostartup:
@stacksofplates said in Configuration for EC2 instance autostartup:
@ambarishrh said in Configuration for EC2 instance autostartup:
May be he is looking for something like https://aws.amazon.com/answers/infrastructure-management/ec2-scheduler/
I don't get that. It seems less flexible than an ELB and you would have to continually calculate what you would need. Why not just pay for the ELB and have it automatically do this?
If you really don't need this type of infrastructure, then just use something like Vultr or DO.
I'm gonna have to read up on the ELB. Looks like exactly the thing I've been wondering why nobody had.
Ya they're pretty awesome. You need to use their monitoring to get the most out of it, but if you are operating at that scale it's worth it anyway.
However, as awesome as it is you have to take into account the vendor lock in you are accepting. Chances are you won’t just be able to migrate to another provider if you need to without significant retooling.
-
@sadee said in Configuration for EC2 instance autostartup:
@stacksofplates
Hi, I need to configure every day the server need to be powered on automatically some time and the same need to be powered off in the evening. Power off i was done through scheduled task in windows. But powering on is the challenge. I tried with lambda option but having some errorInstead of turning the server on and off, might it make sense to just turn the service on and off?
-
@sadee said in Configuration for EC2 instance autostartup:
@stacksofplates
Hi, I need to configure every day the server need to be powered on automatically some time and the same need to be powered off in the evening. Power off i was done through scheduled task in windows. But powering on is the challenge. I tried with lambda option but having some errorAre you trying to save some money on the amount of hours the server is powered on a month?
