Official agent skill

Elastic Beanstalk

by awslabs in awslabs/agent-plugins

Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS).

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Elastic Beanstalk

skills CLI
$ npx skills add awslabs/agent-plugins --skill elastic-beanstalk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install awslabs/agent-plugins elastic-beanstalk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/awslabs/agent-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/deploy-on-aws/skills/elastic-beanstalk .claude/skills/elastic-beanstalk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
elastic-beanstalk
GitHub stars
915
Token cost
~3.1k tokens
SKILL.md length
1,340 words
Files
4 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS).

  • Works in 4 steps: Map to platform - Select the EB platform… → Configure - Environment type (web server… → Generate - AWS CLI commands, CDK, or… → …
  • : elastic beanstalk
  • SKILL.md covers When to Use, Key Distinction, Choose the Mode and Workflow (Standard), plus 6 more sections
  • Calls aws

What it does

Elastic Beanstalk is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS). Triggers on: elastic beanstalk, EB, beanstalk standard, beanstalk cluster, managed EC2 platform, web app with managed patching, worker on EC2, Heroku alternative, don't want to manage servers or container orchestration, migrate from Heroku, managed operational lifecycle, containerised app without operating Kubernetes, several services sharing a managed cluster, managed EKS without kubectl. Covers web…

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/cluster-mode.md`, `references/configuration.md` and `references/platforms.md`).

It sits in DevOps & Cloud, covering Container orchestration. It works with Kubernetes and Amazon Web Services. The repository describes itself as: Agent Plugins for AWS equip AI coding agents with the skills to help you architect, deploy, and operate on AWS. The licence is Apache-2.0.

When your agent uses it

  • : elastic beanstalk
  • Beanstalk standard
  • Beanstalk cluster
  • Managed EC2 platform

Example prompts

  • “/elastic-beanstalk”

Requirements

  • Docker

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Map to platform - Select the EB platform branch (see platforms)
  2. Configure - Environment type (web server or worker), instance size, scaling
  3. Generate - AWS CLI commands, CDK, or Terraform (see IaC section below)
  4. Deploy - Execute with user confirmation

What it can do on your machine

Read from SKILL.md and the folder at commit da51970. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.aws.amazon.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Elastic Beanstalk loads about 3.1k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 1,340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~160
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~16k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from awslabs/agent-plugins at commit da51970, republished under its Apache-2.0 licence (© awslabs). 1,340 words, ~3,066 tokens.

Download SKILL.mdSave it as .claude/skills/elastic-beanstalk/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
elastic-beanstalk
description
Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS). Triggers on: elastic beanstalk, EB, beanstalk standard, beanstalk cluster, managed EC2 platform, web app with managed patching, worker on EC2, Heroku alternative, don't want to manage servers or container orchestration, migrate from Heroku, managed operational lifecycle, containerised app without operating Kubernetes, several services sharing a managed cluster, managed EKS without kubectl. Covers web and worker applications on EC2, and containerised single- and multi-service applications on managed EKS.

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:

SignalMode
Source on a standard runtime; Windows or .NET FrameworkStandard
Worker consuming an SQS queueStandard
Writes uploads, sessions, or working files to local diskStandard
One small application, cost is the priorityStandard
Several services needing private service-to-service trafficCluster
Kubernetes underneath without operating KubernetesCluster
Managed OpenTelemetry, or faster deploys and scalingCluster

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:

  1. Map to platform - Select the EB platform branch (see platforms)
  2. Configure - Environment type (web server or worker), instance size, scaling
  3. Generate - AWS CLI commands, CDK, or Terraform (see IaC section below)
  4. Deploy - Execute with user confirmation
Show full SKILL.md (585 more words)Show less

Defaults

SettingDevProduction
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)
Instancet3.smallt3.medium or larger
DeploymentsAll-at-onceRolling with additional batch
Health reportingEnhancedEnhanced
Managed updatesEnabled (weekly)Enabled (maintenance window)
HTTPS (web only)ACM certificate + ALBACM 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 CodebaseEnvironment Type
HTTP listener, web framework, API routesWeb server
Queue-based consumer, SQS processing, no HTTP servingWorker
HTTP serving + queue-based background processingWeb 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:

  1. aws elasticbeanstalk create-storage-location → returns the S3 bucket (idempotent — returns existing bucket if already created)
  2. aws elasticbeanstalk create-application
  3. Zip source bundle, upload to the bucket from step 1
  4. aws elasticbeanstalk create-application-version
  5. aws elasticbeanstalk create-environment with --option-settings (web: --tier Name=WebServer,Type=Standard, worker: --tier Name=Worker,Type=SQS/HTTP)
  6. aws elasticbeanstalk wait environment-updated
  7. Subsequent 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:PutObject on 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:

ConfigurationEstimated 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

© awslabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in plugins/deploy-on-aws/skills/elastic-beanstalk of awslabs/agent-plugins.

  • SKILL.md
  • references/cluster-mode.md
  • references/configuration.md
  • references/platforms.md

Open the folder on GitHubat commit da51970

Compare with similar skills

Elastic Beanstalk next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Elastic Beanstalk compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Elastic Beanstalk this skillawslabs/agent-plugins915—~3.1kAutomated safety check: PassApache-2.0
Provider Bug Reviewmondoohq/mql412—~2.9kAutomated safety check: PassCustom licence
Kcli Cluster Deploymentkarmab/kcli653—~1.5kAutomated safety check: PassApache-2.0
Hashicorp VaultBagelHole/DevOps-Security-Agent-Skills1.1k—~2kAutomated safety check: PassMIT
Logfire Infrastructurepydantic/skills140—~1.8kAutomated safety check: PassMIT
Eks Best Practicesaws-samples/appmod-blueprints115—~5kAutomated safety check: PassMIT-0

Similar skills

  • Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

    412 GitHub stars~2.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Guides deployment and management of Kubernetes clusters with kcli.

    653 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Hashicorp Vault

    BagelHole/DevOps-Security-Agent-Skills

    Manage secrets and PKI with HashiCorp Vault. An agent skill from BagelHole/DevOps-Security-Agent-Skills.

    1.1k GitHub stars~2k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed
  • Logfire Infrastructure

    pydantic/skills

    Official

    Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.

    140 GitHub stars~1.8k tokensUpdated 8 days ago
    DevOps & CloudAuto-check passed
  • Eks Best Practices

    aws-samples/appmod-blueprints

    Official

    Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.

    115 GitHub stars~5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Extend Discovery Type

    runwhen-contrib/runwhen-local

    Add or enrich a resource type in an existing RunWhen Local discovery indexer (Azure azureapi, GCP gcpapi, AWS, or Kubernetes).

    163 GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from awslabs/agent-plugins

All 33 skills in this repo
  • Dataset Evaluation

    awslabs/agent-plugins

    Official

    Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR).

    915 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Dataset Transformation

    awslabs/agent-plugins

    Official

    Generates code that transforms datasets between ML schemas for model training or evaluation.

    915 GitHub starsUsed in 1 repo~3.5k tokens
    Auto-check passed
  • AWS Lambda Managed Instances

    awslabs/agent-plugins

    Official

    Evaluate, configure, and migrate workloads to AWS Lambda Managed Instances (LMI).

    915 GitHub stars~4k tokensUpdated yesterday
    Auto-check passed
  • Finetuning Technique

    awslabs/agent-plugins

    Official

    Selects a fine-tuning technique (SFT, DPO, RLVR, or RLAIF) for the user's use case and validates it against the selected model's available recipes.

    915 GitHub stars~604 tokensUpdated yesterday
    Auto-check passed
  • Hyperpod Issue Report

    awslabs/agent-plugins

    Official

    Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases.

    915 GitHub stars~890 tokensUpdated yesterday
    Auto-check passed
  • Hyperpod Performance Debugger

    awslabs/agent-plugins

    Official

    Diagnose performance issues on Amazon SageMaker HyperPod clusters — uneven NCCL bandwidth across nodes and poor filesystem throughput.

    915 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Elastic Beanstalk

What does Elastic Beanstalk do?

Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS). Elastic Beanstalk is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS).

When should I use Elastic Beanstalk?

Elastic Beanstalk fits situations like: : elastic beanstalk; beanstalk standard; beanstalk cluster; managed EC2 platform.

How do I install Elastic Beanstalk in Claude Code?

Run `npx skills add awslabs/agent-plugins --skill elastic-beanstalk -a claude-code`. Or copy the skill folder (plugins/deploy-on-aws/skills/elastic-beanstalk in awslabs/agent-plugins) into .claude/skills/elastic-beanstalk in your project. Claude Code loads it when a task matches its description.

How do I install Elastic Beanstalk in Codex?

Run `npx skills add awslabs/agent-plugins --skill elastic-beanstalk -a codex`. Or copy the skill folder (plugins/deploy-on-aws/skills/elastic-beanstalk in awslabs/agent-plugins) into .agents/skills/elastic-beanstalk in your project. Codex loads it when a task matches its description.

Can I use Elastic Beanstalk in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add awslabs/agent-plugins --skill elastic-beanstalk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/elastic-beanstalk, .gemini/skills/elastic-beanstalk, .github/skills/elastic-beanstalk and .opencode/skills/elastic-beanstalk in your project.

What does Elastic Beanstalk need to run?

Going by SKILL.md and its folder, Elastic Beanstalk needs the command-line tools its instructions call (aws). Our summary lists: Docker.

Does Elastic Beanstalk access the network?

SKILL.md names 1 domain. As links in the text: docs.aws.amazon.com. This is read from the text; nothing was executed.

Is Elastic Beanstalk safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Elastic Beanstalk use?

Elastic Beanstalk is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Elastic Beanstalk use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Elastic Beanstalk?

Skills that share tags, products or a category with Elastic Beanstalk: Provider Bug Review (mondoohq/mql, 412 stars), Kcli Cluster Deployment (karmab/kcli, 653 stars), Hashicorp Vault (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars) and Logfire Infrastructure (pydantic/skills, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Elastic Beanstalk?

awslabs (a GitHub organization, an official publisher) maintains it in awslabs/agent-plugins, which has 915 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.

Source: awslabs/agent-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.