[go: up one dir, main page]

Jump to content

AWS Elastic Beanstalk

From Wikipedia, the free encyclopedia
Developer(s)Amazon Web Services
Initial releaseJanuary 19, 2011[1]
TypeWeb development
LicenseProprietary
Websiteaws.amazon.com/elasticbeanstalk/

AWS Elastic Beanstalk is an orchestration service offered by Amazon Web Services for deploying applications which orchestrates various AWS services, including EC2, S3, Simple Notification Service (SNS), CloudWatch, autoscaling, and Elastic Load Balancers.[2] Elastic Beanstalk provides an additional layer of abstraction over the bare server and OS; users instead see a pre-built combination of OS and platform, such as "64bit Amazon Linux 2014.03 v1.1.0 running Ruby 2.0 (Puma)" or "64bit Debian jessie v2.0.7 running Python 3.4 (Preconfigured - Docker)".[3] Deployment requires a number of components to be defined: an 'application' as a logical container for the project, a 'version' which is a deployable build of the application executable, a 'configuration template' that contains configuration information for both the Beanstalk environment and for the product.[4] Finally an 'environment' combines a 'version' with a 'configuration' and deploys them.[3] Executables themselves are uploaded as archive files to S3 beforehand and the 'version' is just a pointer to this.[3]

Name

[edit]

The name "Elastic beanstalk" is a reference to the beanstalk that grew all the way up to the clouds in the fairy tale Jack and the Beanstalk.

Applications and software stacks

[edit]

Supported applications and software stacks include:[5]

Alternative AWS technologies

[edit]

References

[edit]
  1. ^ "Release: AWS Elastic Beanstalk". Retrieved 2013-05-06.
  2. ^ "What Is AWS Elastic Beanstalk and Why Do I Need It?". Retrieved 2013-05-27.
  3. ^ a b c Wittig, Andreas; Wittig, Michael (2016). Amazon Web Services in Action. Manning Press. p. 132-133. ISBN 978-1-61729-288-0.
  4. ^ "AWS Elastic Beanstalk: deployment options". 5 January 2022.
  5. ^ "AWS Elastic Beanstalk FAQ". Retrieved 2020-03-17.
  6. ^ AWS in Action & Wittig (2016), p. 112.
[edit]