We started the compute layer on Day 13 with EC2, ELB, and Auto Scaling — where you launch and manage everything yourself. Today we move one level up the abstraction ladder: services where AWS takes over more of the operational burden. By the end of this post you'll know what each one does, how it differs from plain EC2, and when to actually reach for it.
AWS Elastic Beanstalk
Elastic Beanstalk is a Platform-as-a-Service (PaaS) offering built on top of EC2. You upload your application code and a bit of configuration; Beanstalk provisions the EC2 instances, load balancer, and Auto Scaling Group for you.
The IaaS/PaaS/SaaS framing from Day 13 explains why this exists: with EC2 you cook the meal yourself, with Beanstalk you eat at a restaurant — someone else runs the kitchen. In practice, that means you pick a platform (Tomcat for Java, .NET, Python, Docker, Go, and so on), upload your application, and Beanstalk launches and manages the EC2 instances behind the scenes, handing you back a URL.
One nuance worth calling out: in general, PaaS means you have zero control over the underlying servers. Beanstalk is a bit more generous than that — you still have full access to the EC2 instances it creates, you can SSH in and tweak things, Beanstalk just manages the lifecycle for you instead of you doing it manually.
