elastic-beanstalk

1# Elastic Beanstalk
2 
3Deploy applications to production on AWS with full lifecycle management. Elastic
4Beanstalk is an application management service: the user provides application
5code or a container image, AWS manages everything underneath (deployment,
6scaling, patching, monitoring, health response).
7 
8There are two modes, and the choice determines every setting that follows.
9**Standard** runs the application on Amazon EC2; **Cluster** runs a container on
10a managed Amazon EKS Auto Mode cluster. See [Choose the Mode](#choose-the-mode).
11 
12## When to Use
13 
14Elastic Beanstalk is the right choice when:
15 
16- User explicitly asks for Elastic Beanstalk, EB, or a managed application platform
17- User says "don't want to manage servers", "managed patching", or "Heroku-like"
18- User is migrating from Heroku, Render, or Railway
19- User wants AWS to manage ongoing operational lifecycle (patching, scaling,
20  health monitoring, rollback, deployments) after initial setup
21- App is a web framework, API, or background worker on a standard runtime and
22  the user signals low infrastructure involvement
23 
24Elastic Beanstalk is NOT the right choice when:
25 
26- User explicitly wants serverless/Lambda — this imposes a different programming
27  model (event-driven functions, stateless, cold starts, 15-min max execution)
28  rather than just eliminating server management
29- User wants fine-grained container orchestration control (use ECS)
30- User already has Kubernetes expertise and wants direct K8s access (use EKS)
31…