Elastic Beanstalk
AWS LabsOfficialPublished by AWS Labs
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Elastic Beanstalk is an application management service that handles the operational lifecycle of your code or container images, including deployment, scaling, patching, and health monitoring. It offers two distinct modes: Standard, which runs applications on Amazon EC2 instances, and Cluster, which runs containerized applications on a managed Amazon EKS Auto Mode cluster. The service is designed for users who want to avoid managing underlying infrastructure while maintaining a standard application programming model.
What it does
- Deploys web and worker applications using either EC2 (Standard) or managed EKS (Cluster) infrastructure.
- Automates operational tasks like scaling, patching, health monitoring, and deployment rollbacks.
- Supports configuration via AWS CLI, CDK, or Terraform for infrastructure-as-code workflows.
- Provides managed HTTPS termination and load balancing for web environments.
- Integrates with AWS Secrets Manager for secure environment variable injection.
- Enables custom lifecycle hooks and environment configuration via platform-specific settings.
When to use it
- When you need a managed application platform and want to avoid manual server or container orchestration.
- When migrating applications from platforms like Heroku, Render, or Railway to AWS.
- When you require a managed operational lifecycle for web frameworks, APIs, or background workers.
- When you need to run containerized applications on Kubernetes without managing the cluster yourself.
- When you prefer a standard application programming model over the constraints of serverless functions.
Advantages
- Reduces ongoing maintenance overhead by offloading operational responsibility to AWS.
- Supports both traditional EC2-based deployments and modern containerized EKS workflows.
- Maintains standard application programming models (e.g., long-running processes, local state).
- Provides flexible deployment policies including rolling and immutable updates for zero-downtime.
- Offers consistent infrastructure-as-code support across different deployment modes.
Usage examples
- “Deploy my Python web application to Elastic Beanstalk.”
- The agent will analyze the codebase, select the appropriate Standard mode platform, configure the environment, and execute the deployment workflow.
- “I need to migrate my containerized multi-service app from Heroku to AWS without managing Kubernetes.”
- The agent will verify the application contract for Cluster mode and set up a managed EKS environment to host the services.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/awslabs/elastic-beanstalk/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip elastic-beanstalk.zip -d .agents/skills
Documentation by AWS Labs
Elastic Beanstalk
Deploy applications to production on AWS with full lifecycle management. Elastic Beanstalk is an application management service: the user provides application code or a container image, AWS manages everything underneath (deployment, scaling, patching, monitoring, health response).
There are two modes, and the choice determines every setting that follows. Standard runs the application on Amazon EC2; Cluster runs a container on a managed Amazon EKS Auto Mode cluster. See Choose the Mode.
When to Use
Elastic Beanstalk is the right choice when:
User explicitly asks for Elastic Beanstalk, EB, or a managed application platform
User says "don't want to manage servers", "managed patching", or "Heroku-like"
User is migrating from Heroku, Render, or Railway
User wants AWS to manage ongoing operational lifecycle (patching, scaling, health monitoring, rollback, deployments) after initial setup
App is a web framework, API, or background worker on a standard runtime and the user signals low infrastructure involvement
Elastic Beanstalk is NOT the right choice when:
User explicitly wants serverless/Lambda — this imposes a different programming model (event-driven functions, stateless, cold starts, 15-min max execution) rather than just eliminating server management
User wants fine-grained container orchestration control (use ECS)
User already has Kubernetes expertise and wants direct K8s access (use EKS)
App is a static site or SPA (use Amplify Hosting for the frontend; deploy the backend API separately if present)
User already has ECS task definitions or Fargate configuration
Key Distinction
ECS and EKS are infrastructure management services: the user defines and operates the deployment infrastructure (task definitions, services, clusters, scaling policies) and owns ongoing operational decisions. Elastic Beanstalk is an application management service: the user provides source code or a Docker image, and AWS provisions and operates the production environment on an ongoing basis. The result is the same reliability, but with lower ongoing maintenance cost because operational responsibility stays with the provider.
Both models support IaC (CDK, CloudFormation, Terraform). The distinction is not about tooling — it is about who manages the lifecycle after deployment.
Lambda/serverless is a different axis entirely. "Don't want to manage servers" does not mean "wants serverless" — Elastic Beanstalk also eliminates server management while preserving the standard application programming model (long-running processes, persistent connections, threads, and — in Standard mode only — local state; Cluster mode replicas have ephemeral local storage). Serverless imposes a specific programming model: stateless functions, cold starts, event-driven invocation, and a 15-minute execution ceiling. Route to Lambda only when the user explicitly asks for serverless or the workload is natively event-driven (e.g., S3 triggers, API Gateway request/response with no session state).
Choose the Mode
Decide before generating anything. The modes share an API and nothing else: a Standard mode namespace passed to a Cluster mode environment is rejected, not ignored.
Cluster mode has an entry requirement, and it is checked first. Route to Cluster only when every service can run as identical, interchangeable replicas and all durable state — uploads, sessions, caches, working files — already lives outside the container. Replica local storage is ephemeral and is lost on every restart, and there is no persistent volume option. An application that fails this goes to Standard mode, or gets changed first; a multi-service signal does not override it. See the application contract.
Then the signals:
| Signal | Mode |
|---|---|
| Source on a standard runtime; Windows or .NET Framework | Standard |
| Worker consuming an SQS queue | Standard |
| Writes uploads, sessions, or working files to local disk | Standard |
| One small application, cost is the priority | Standard |
| Several services needing private service-to-service traffic | Cluster |
| Kubernetes underneath without operating Kubernetes | Cluster |
| Managed OpenTelemetry, or faster deploys and scaling | Cluster |
A container image alone does not settle it, because Standard mode has a Docker platform too — ask. Prefer Cluster mode when the application is containerised, multi-service, and meets the contract above, since environments sharing subnets share one cluster and reach each other privately. Prefer Standard for a single container where a cluster is not yet justified. Do not propose migrating a working Standard environment unless asked: there is no in-place conversion, only new environments and a CNAME swap.
If the mode is Cluster, follow cluster mode and stop here. Everything below is Beanstalk Standard.
Workflow (Standard)
This skill is invoked after the deploy skill selects Elastic Beanstalk as the deployment target. The deploy skill handles codebase analysis and cost estimation. This skill handles EB-specific configuration:
Map to platform - Select the EB platform branch (see platforms)
Configure - Environment type (web server or worker), instance size, scaling
Generate - AWS CLI commands, CDK, or Terraform (see IaC section below)
Deploy - Execute with user confirmation
Defaults
| Setting | Dev | Production |
|---|---|---|
| Environment type (web) | Load-balanced (min=1, max=1) | Load-balanced, Multi-AZ |
| Environment type (worker) | Auto Scaling group (min=1, max=1) | Auto Scaling group (min=2, max=4) |
| Instance | t3.small | t3.medium or larger |
| Deployments | All-at-once | Rolling with additional batch |
| Health reporting | Enhanced | Enhanced |
| Managed updates | Enabled (weekly) | Enabled (maintenance window) |
| HTTPS (web only) | ACM certificate + ALB | ACM certificate + ALB |
Default to dev unless user says "production" or "prod".
Always use load-balanced environments for web server types. This ensures instances stay in private subnets behind an ALB, HTTPS terminates via ACM automatically, and scaling up later is a config change rather than an environment type migration. Dev deployments with min=max=1 cause brief downtime on deploy (single instance, all-at-once). If zero-downtime dev is needed, use min=1 max=2 with rolling.
Worker environments do not have load balancers — they receive work from SQS and are scaled via Auto Scaling group settings.
Environment Types
| Signal in Codebase | Environment Type |
|---|---|
| HTTP listener, web framework, API routes | Web server |
| Queue-based consumer, SQS processing, no HTTP serving | Worker |
| HTTP serving + queue-based background processing | Web server + separate Worker environment |
Worker environments receive work via an SQS queue managed by Elastic Beanstalk.
EB's SQS daemon sends HTTP POST requests to the application at a configurable
path (default: POST /). The application must expose this HTTP endpoint to
process each message — no SQS SDK integration required.
Worker environments also support periodic tasks via cron.yaml for scheduled
jobs (alternative to EventBridge + Lambda when the user is already using EB).
If the app uses in-process background threads or async tasks (not queue-based), a single web server environment is sufficient — do not create a separate Worker.
IaC Generation
Default: AWS CLI — no extra tooling to install. The agent orchestrates the multi-step workflow:
aws elasticbeanstalk create-storage-location→ returns the S3 bucket (idempotent — returns existing bucket if already created)aws elasticbeanstalk create-applicationZip source bundle, upload to the bucket from step 1
aws elasticbeanstalk create-application-versionaws elasticbeanstalk create-environmentwith--option-settings(web:--tier Name=WebServer,Type=Standard, worker:--tier Name=Worker,Type=SQS/HTTP)aws elasticbeanstalk wait environment-updatedSubsequent deploys: new version +
update-environment
Resolve the --solution-stack-name by running
aws elasticbeanstalk list-available-solution-stacks and filtering for the
detected platform (e.g., ".NET" + "Amazon Linux 2023"). Alternatively, use
--platform-arn from aws elasticbeanstalk list-platform-versions.
Use .ebextensions/ and platform hooks for customization.
See AWS CLI EB reference for full command documentation.
Override: CDK (TypeScript) when the user has an existing CDK project, wants repeatable IaC, or explicitly requests it:
CfnApplication,CfnEnvironment,CfnConfigurationTemplate
Override: Terraform when the user's repo already has Terraform:
aws_elastic_beanstalk_application,aws_elastic_beanstalk_environment
CDK and Terraform templates are scannable by cfn-nag/checkov pre-deploy.
Security
Apply these automatically:
Web server instances in private subnets behind ALB
Worker instances in private subnets with NAT Gateway for outbound
HTTPS via ACM certificate on ALB (web server environments)
IAM instance profile with least-privilege permissions — scan source code for AWS SDK client usage to determine required actions (e.g.,
AmazonBedrockRuntimeClient→bedrock:InvokeModel,AmazonS3Client→s3:GetObject/s3:PutObjecton specific buckets)Enhanced health reporting enabled
Managed platform updates enabled
Security groups: ALB accepts 443, instances accept only from ALB
See the deploy skill's security defaults for encryption, VPC placement, and IAM patterns.
Cost
Elastic Beanstalk has no service fee. Cost = underlying AWS resources. Query the awspricing MCP server for region-accurate estimates. Approximate us-east-1 pricing:
| Configuration | Estimated Monthly Cost |
|---|---|
| Dev web (1x t3.small + ALB) | ~$35-40 |
| Dev worker (1x t3.small, no ALB) | ~$15-20 |
| Production web (4x t3.medium + ALB, Multi-AZ) | ~$150-200 |
Add RDS/Aurora costs separately if database is included.
References
Beanstalk Cluster mode — containers on managed EKS
Supported platforms and detection — Standard mode
Configuration and customization — Standard mode
Files
- ATTRIBUTION.mdAdded by AutoGineer919 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer89 B
- SKILL.md12.0 KiB
- references/cluster-mode.md39.8 KiB
- references/configuration.md5.5 KiB
- references/platforms.md3.4 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS Labs
- Publisher
- AWS Labs (Official)
- Source
- awslabs/agent-plugins · plugins/deploy-on-aws/skills/elastic-beanstalk · commit fbefb37
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS Labs.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download elastic-beanstalk.zip