This has been an exciting week as London is starting to open up little by little. We agreed with the rest of my team at work that whoever wants can start to the office twice per week. Finally after a long winter of staying at home the whole day every day, we can start seeing some people again. The only downside of it is that it broke my routine of tweeting about AWS services.

In this blog post we’re going to talk about Beanstalk which is a really interesting service as it can glue the majority of the stuff you need when creating an environment. I don’t understand why not everyone uses it.

Definitely once I finish this project and get my certification this will be one of the first services that I’m going to dive deep into it. Without further ado let’s check it out.

AWS Beanstalk

What is AWS Elastic Beanstalk?

• A platform as a service for deploying applications to AWS
• It is a layer for configuring how to use other services like EC2, Auto Scaling Groups, Load Balancers, RDS etc.
• Using Elastic Beanstalk is free but you only pay for the underlying resources
• Elastic Beanstalk is a managed service and can also be used for deployment strategies
• The idea behind it is that the developer is responsible for the code and Beanstalk for the infrastructure

There are 3 architecture models

1. Single Instance Deployment which is great for dev environments
2. Load Balancer with Auto Scaling Groups which is the standard model for production web apps
3. Auto Scaling Groups only which is mainly for analytics and workers services