Skip to content

opensite-ai/opensite-skills / aws-containers

aws-containers

Verified

Builds, deploys, debugs, and optimizes containerized workloads on Amazon EKS, ECS, Fargate, ECR, and Elastic Beanstalk. Covers EKS operations and add-ons; ECS task definitions, services, Exec, Express Mode, Managed Instances, and Action Logs; ECR repositories and lifecycle policies; and Elastic Beanstalk platforms plus Beanstalk Cluster Mode for running containerized applications on service-managed EKS compute. Use for container deployment, service selection, configuration, scaling, health, troubleshooting, image workflows, or deciding between Beanstalk-managed Cluster Mode and direct EKS. Should be used instead of relying on internal knowledge for these services.

references/beanstalk-platforms.md

View on GitHub
# Elastic Beanstalk - Supported Platforms

These rules apply only after an EC2-based Elastic Beanstalk platform has been
selected. For Beanstalk Cluster Mode, read
[beanstalk-cluster-mode.md](beanstalk-cluster-mode.md) instead.

Detect the application's language and framework, then map to an EB platform branch.

## Platform Detection

| Signal in Codebase                              | EB Platform            | Notes                          |
| ----------------------------------------------- | ---------------------- | ------------------------------ |
| `requirements.txt`, `Pipfile`, `pyproject.toml` | Python on AL2023       | Django, Flask, FastAPI         |
| `package.json` (backend Node.js)                | Node.js on AL2023      | Express, NestJS, Fastify, Hono |
| `pom.xml`, `build.gradle`, `.jar`               | Corretto on AL2023     | Spring Boot, Quarkus           |
| `pom.xml`, `build.gradle`, `.war`               | Tomcat on AL2023       | WAR-based Java web apps        |
| `Gemfile`, `config.ru`                          | Ruby on AL2023         | Rails, Sinatra                 |
| `go.mod`                                        | Go on AL2023           | Any Go HTTP server             |
| `*.csproj`, `*.sln` (ASP.NET Core)              | .NET on AL2023         | ASP.NET Core on Linux          |
| `*.csproj`, `*.sln` (.NET Framework)            | .NET on Windows Server | IIS, .NET Framework 4.x        |
| `composer.json`                                 | PHP on AL2023          | Laravel, Symfony               |
| `Dockerfile`                                    | Docker on AL2023       | Any containerized app          |

## Platform Selection Rules

1. If `Dockerfile` exists AND a language runtime is also detected, ask the user for an explicit selection.
2. If multiple languages detected, ask the user for an explicit selection.
3. Always use Amazon Linux 2023 unless the app requires Windows (.NET Framework,
   IIS dependencies).
4. For Java apps: if `.war` file, deploy to Tomcat platform. If `.jar` with
   embedded server (Spring Boot), use Corretto platform.
5. Always use the latest supported runtime version unless the application
   specifies a version constraint (e.g., `engines` in `package.json`,
   `<TargetFramework>` in `.csproj`).

## Supported Deployment Artifacts

| Platform           | Accepted Input                                        |
| ------------------ | ----------------------------------------------------- |
| Language platforms | Source bundle (zip of source code)                    |
| .NET               | Published output (`dotnet publish` zip, not source)   |
| Java (.jar)        | Built artifact (fat jar or exploded directory)        |
| Docker             | Source bundle containing Dockerfile                   |
| Docker (pre-built) | Dockerfile with `FROM` referencing ECR/registry image |

.NET and Java platforms require pre-built artifacts. Run `dotnet publish` or
`mvn package`/`gradle build` before zipping. Other language platforms (Python,
Node.js, Ruby, Go, PHP) accept raw source and build on-instance.

## Worker Platform Considerations

Worker environments use the same platforms as web server environments. The
difference is the SQS daemon that delivers messages to the application over HTTP
on `localhost`. The application must expose an HTTP endpoint (default: `POST /`)
that processes each message.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall