0

I created a elastic beanstalk environment and it created an EC2 instance. Then I thought I don't actually need this yet so I'll stop the EC2 instance, but then it seemed to start another one.

So my question is if I have an EB instance will I be charged by the hour for the underlying EC2 image all the time or only when the the service it provides is being access via the public elasticip. And if Im charged all the time is there a way to halt a elastic beanstalk application or only delete it or instantiate to a new environment.

Paul Taylor
  • 13,411
  • 42
  • 184
  • 351

1 Answers1

0

The auto scaling feature of Elastic Beanstalk will automatically start another instance if a current instance continues to fail a health check. Stopping individual instances outside of the environment will cause failed health checks and trigger a new instance to be spun up.

You will be charged when the components within the environment are running as stated by Amazon here:

There is no additional charge for Elastic Beanstalk – you only pay for the underlying AWS resources (e.g. Amazon EC2, Amazon S3) that your application consumes.

You can completely stop an environment through the CLI. I gave this answer to a previous question about starting and stopping Elastic Beanstalk:

The EB command line interface has an eb stop command. Here is a little bit about what the command actually does:

The eb stop command deletes the AWS resources that are running your application (such as the ELB and the EC2 instances). It however leaves behind all of the application versions and configuration settings that you had deployed, so you can quickly get started again. Eb stop is ideal when you are developing and testing your application and don’t need the AWS resources running over night. You can get going again by simply running eb start.

Community
  • 1
  • 1
EFeit
  • 2,082
  • 16
  • 29
  • thanks, bit silly that its not available from the website though, but perhaps that is done on purpose to make Amazon some extra dosh. – Paul Taylor Jun 26 '14 at 15:02
  • You _can_ use the website. You simply need to terminate the entire environment from within the Elastic Beanstalk tab of the AWS Console, instead of the EC2 tab. – Ryan Parman Jun 28 '14 at 22:29