Agent skill · DevOps & Cloud

elastic-beanstalk

Deploy to AWS Elastic Beanstalk. Triggers on: elastic beanstalk, EB, 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. Covers Elastic Beanstalk on EC2 for web and worker applications.

Amazon Web Services - Labs12,649★ · +18/wk · 2 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add awslabs/agent-plugins --skill elastic-beanstalk --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: plugins/deploy-on-aws/skills/elastic-beanstalk/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 850
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Elastic Beanstalk Deploy web and worker applications to production on AWS with full lifecycle management. Elastic Beanstalk is an application management service: the user provides application code, AWS manages everything underneath (deployment, scaling, patching, monitoring, health response). ## 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 an

What's inside
Steps it walks through
  1. When to Use
  2. Key Distinction
  3. Workflow
  4. Defaults
  5. Environment Types
  6. IaC Generation
  7. Security
  8. Cost
  9. References
Ships with 2 files
  • references/configuration.md
  • references/platforms.md
More from agent-plugins
All skills →
About this skill
What does the elastic-beanstalk skill do?

Deploy to AWS Elastic Beanstalk. Triggers on: elastic beanstalk, EB, 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. Covers Elastic Beanstalk on EC2 for web and worker applications.

How do I install it?

Run `npx skills add awslabs/agent-plugins --skill elastic-beanstalk --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From awslabs/agent-plugins, a repository with 850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going