Choose AWS compute by workload shape and operational burden: Lambda (event/spiky), Fargate/ECS Express Mode (containers, no cluster ops), EKS (k8s/portability), EC2 (legacy/specific); design event-driven integration with idempotency and DLQs.
Scanned 9/25/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill aws-compute-selection --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Aws Compute Selection?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-aws-compute-selection)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: aws-compute-selection
description: "Choose AWS compute by workload shape and operational burden: Lambda (event/spiky), Fargate/ECS Express Mode (containers, no cluster ops), EKS (k8s/portability), EC2 (legacy/specific); design event-driven integration with idempotency and DLQs."
---
# AWS Compute Selection
| Workload | Compute |
|---|---|
| Event / spiky / short | **Lambda** |
| Long-running container, no cluster ops | **Fargate / ECS Express Mode** |
| Need k8s / portability | **EKS** |
| Legacy / specific OS | **EC2** |
Match the shape; don't default to one. Serverless-first for variable load (mind cold starts + limits). App Runner is closed to new customers since 2026-04-30 (maintenance mode); ECS Express Mode (GA re:Invent 2025) is AWS's recommended replacement, though it has no scale-to-zero.
## Integration
SQS (decouple), SNS/EventBridge (fan-out/route), **Step Functions** (orchestrate w/ retries). Every async consumer is **idempotent** + has a **DLQ**. No hand-rolled queues/pollers.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
