Use this skill when architecting on AWS, selecting services, optimizing costs, or following the Well-Architected Framework. Triggers on EC2, S3, Lambda, RDS, DynamoDB, CloudFront, IAM, VPC, ECS, EKS, SQS, SNS, API Gateway, and any task requiring AWS architecture decisions, service selection, or cost management.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
cloud-aws
version
0.1.0
description
Use this skill when architecting on AWS, selecting services, optimizing costs, or following the Well-Architected Framework. Triggers on EC2, S3, Lambda, RDS, DynamoDB, CloudFront, IAM, VPC, ECS, EKS, SQS, SNS, API Gateway, and any task requiring AWS architecture decisions, service selection, or cost management.
When this skill is activated, always start your first response with the 🧢 emoji.
AWS Cloud Architecture
A practical guide to building production systems on AWS following the
Well-Architected Framework. This skill covers service selection, VPC design, IAM
least-privilege, serverless patterns, cost optimization, and monitoring - with
an emphasis on when to use each service, not just how. Designed for engineers
who know AWS basics and need opinionated guidance on trade-offs and common pitfalls.
Designs or reviews a VPC, subnet, or security group setup
Needs IAM roles, policies, or permission boundaries
Architects a serverless application (API Gateway + Lambda + DynamoDB)
Asks about cost reduction, Reserved Instances, Savings Plans, or right-sizing
Sets up CloudWatch alarms, dashboards, or log insights
Selects a database service (RDS, Aurora, DynamoDB, ElastiCache)
Plans multi-region or high-availability architecture
Do NOT trigger this skill for:
General Linux/shell scripting unrelated to AWS
Kubernetes internals that are cloud-agnostic (use a k8s skill instead)
Key principles
Operational excellence - Automate everything that can be automated.
Infrastructure-as-code (CloudFormation, CDK, Terraform) is not optional. Every
change should be reviewable, reproducible, and reversible. Run post-incident
reviews and feed learnings back into runbooks.
Security - Apply least-privilege IAM everywhere. No * actions in production
policies. Encrypt data at rest (KMS) and in transit (TLS). Treat every AWS account
boundary as a trust boundary. Use VPC endpoints to keep traffic off the public
internet where possible.
Reliability - Design for multi-AZ by default. Use health checks, auto-scaling,
and managed services that handle failure transparently. Define Recovery Time
Objective (RTO) and Recovery Point Objective (RPO) before choosing a database tier.
Performance efficiency - Right-size before you scale out. Understand the
access patterns of your workload and match them to the service that handles them
natively (e.g., DynamoDB for key-value at scale, Aurora for relational OLTP).
Use CloudFront and edge caching to reduce origin load.
Cost optimization - Cost is an architecture decision, not an afterthought.
Tag every resource. Use Cost Explorer weekly. Commit to Reserved Instances or
Savings Plans for stable workloads. Delete idle resources aggressively.
Core concepts
Regions and Availability Zones
A region is a geographic area with multiple isolated data centers. Each region
contains at least 3 Availability Zones (AZs) - physically separate facilities
with independent power and networking. Deploy stateful services across 2+ AZs for
high availability. Some services (S3, IAM, CloudFront) are global; most are regional.
IAM model
IAM has four building blocks:
Concept
What it is
Principal
Who is acting (user, role, service)
Policy
JSON document defining allowed/denied actions
Role
Identity assumed by services or users (no long-term credentials)
Trust policy
Who is allowed to assume a role
The golden rule: use roles, not users. EC2 instances, Lambda functions, and ECS
tasks all assume roles at runtime. Never embed access keys in code or AMIs.
Compute spectrum
Control / Cost Managed / Speed
<------------------------------------------>
EC2 -> ECS on EC2 -> ECS Fargate -> Lambda -> App Runner
EC2 - full OS control, GPU support, long-running workloads
ECS on EC2 - containerized, you manage the host fleet
Lambda - event-driven, sub-second billing, 15-min max duration
App Runner - HTTP services from container or source, zero infra management
Storage tiers
Service
Use case
S3 Standard
Frequently accessed objects
S3 Intelligent-Tiering
Unpredictable access patterns
S3 Glacier Instant
Archives needing millisecond retrieval
EBS
Block storage attached to EC2
EFS
Shared POSIX filesystem across multiple EC2s
Networking primitives
A VPC is a logically isolated network. Inside it, subnets span a single AZ.
Public subnets have a route to an Internet Gateway; private subnets do not.
Security groups are stateful firewalls attached to ENIs (deny by default).
NACLs are stateless subnet-level firewalls (less common). Use VPC endpoints
to reach AWS services (S3, DynamoDB, SQS) without traversing the internet.
Common tasks
Choose the right compute service
Workload type
Recommended service
Why
Long-running stateful app, GPU needed
EC2
Full OS control, persistent storage
Containerized microservice, >15 min tasks
ECS Fargate
No host management, predictable billing
Event-driven, short tasks (<15 min)
Lambda
Pay-per-invocation, auto-scales to zero
HTTP API from container, zero-ops
App Runner
Automated deployments, TLS, scaling
Large-scale batch processing
AWS Batch on Fargate
Managed job queues, spot support
Kubernetes required
EKS
When you need k8s primitives or portability
Decision rule: start with Lambda or Fargate. Move to EC2 only when you need control
over the OS, persistent GPU, or a runtime Lambda does not support.
Design a VPC with public/private subnets
A standard 3-tier VPC layout:
VPC 10.0.0.0/16
Public subnets (10.0.0.0/24, 10.0.1.0/24, 10.0.2.0/24) - one per AZ
- Internet Gateway route
- Load balancers, NAT Gateways, bastion hosts
Private subnets (10.0.10.0/24, 10.0.11.0/24, 10.0.12.0/24) - one per AZ
- Application servers, ECS tasks, Lambda (VPC-attached)
- Route outbound through NAT Gateway in the public subnet
Database subnets (10.0.20.0/24, 10.0.21.0/24, 10.0.22.0/24) - one per AZ
- RDS, ElastiCache
- No internet route at all
CIDR planning rules:
Use /16 for the VPC to leave room for growth
Use /24 per subnet (251 usable IPs - AWS reserves 5 per subnet)
Reserve CIDR ranges to avoid conflicts with on-premises networks or VPC peering
Never put application workloads in public subnets. Only load balancers and NAT
Gateways belong in public subnets.
Set up IAM roles with least privilege
Start from zero-permissions and add only what's needed. Example Lambda role that
reads from one S3 bucket and writes to DynamoDB:
Scope Resource to specific ARNs, never "*" for data plane actions
Use permission boundaries to cap what a role can grant to child roles
Use IAM Access Analyzer to find overly permissive policies automatically
Rotate any long-term credentials (access keys) every 90 days or eliminate them
Design a serverless API
Standard pattern: API Gateway -> Lambda -> DynamoDB
Client
-> API Gateway (REST or HTTP API)
- Request validation, auth (Cognito/JWT authorizer), throttling
-> Lambda function (per route or single handler)
- Business logic, input validation
-> DynamoDB table
- Partition key = entity type + ID, sort key = operation/timestamp
-> (optional) SQS for async fan-out, SNS for notifications
Choose HTTP API over REST API unless you need WAF integration, edge caching via
API Gateway caches, or request/response transformation. HTTP API costs ~70% less.
DynamoDB access pattern design:
Define all queries before designing the table (single-table design when possible)
Use a composite sort key to support range queries (STATUS#TIMESTAMP)
Enable DynamoDB Streams if downstream Lambdas need to react to changes
Optimize costs
Strategy
When to apply
Typical saving
Reserved Instances (1yr no-upfront)
EC2/RDS running >8h/day, stable size
~30-40%
Compute Savings Plans
Any EC2/Fargate/Lambda, flexible family
~20-30%
Spot Instances
Batch, stateless, fault-tolerant workloads
~60-80%
Right-sizing
Instances with <20% avg CPU over 2 weeks
Varies
S3 Intelligent-Tiering
Objects with unpredictable access
~40% for cold data
Delete idle resources
Unattached EBS volumes, old snapshots, unused EIPs
Immediate
Cost hygiene checklist:
Set up AWS Budgets with alerts at 80% and 100% of monthly target
Enable Cost Allocation Tags and tag every resource with env, team, service
Review Trusted Advisor weekly for underutilized resources
Use Lambda Power Tuning to find the optimal memory/cost configuration
Set up monitoring
Build three layers of observability using CloudWatch:
Metrics - Enable detailed monitoring (1-min granularity) for production EC2.
For Lambda, track Errors, Throttles, Duration, and ConcurrentExecutions.
Dashboards - One dashboard per service with: error rate, latency (p50/p99),
throughput, and saturation (CPU %, queue depth). Use CloudWatch Contributor Insights
to find the top contributors to errors or high latency.
Logs - Use structured JSON logging. Query with CloudWatch Logs Insights:
fields @timestamp, @message
| filter @message like /ERROR/
| stats count() by bin(5m)
Choose a database service
Need
Service
Notes
Relational, OLTP, <100k writes/s
RDS (PostgreSQL/MySQL)
Familiar SQL, managed backups
Relational, high throughput, auto-scaling storage
Aurora
5x MySQL throughput, Global Database for multi-region
Key-value / document at any scale
DynamoDB
Single-digit ms at any scale, requires upfront access pattern design
In-memory caching, session store
ElastiCache (Redis)
Sub-ms reads, Lua scripting, pub/sub
Full-text search
OpenSearch Service
Elasticsearch-compatible, managed
Analytical queries (OLAP)
Redshift
Columnar, petabyte-scale
Graph traversals
Neptune
Gremlin/SPARQL, highly connected data
Decision rule: if access patterns are known and throughput exceeds RDS capacity,
use DynamoDB. If you need joins, aggregations, or ad-hoc SQL, use Aurora.
Anti-patterns / common mistakes
Mistake
Why it's wrong
What to do instead
Using * in IAM policies
Grants unintended access, violates least privilege
Scope to specific actions and ARNs; use IAM Access Analyzer
Putting databases in public subnets
Direct internet exposure, no network-layer defense
Database subnets with no internet route; security groups scoped to app tier
Hardcoding AWS credentials in code
Credentials leak via source control, logs, or container images
Use IAM roles assigned to compute resources; retrieve secrets from Secrets Manager
Single-AZ RDS in production
One maintenance event or hardware failure causes downtime
Enable Multi-AZ deployments; use Aurora for automatic failover
Lambda functions without concurrency limits
Runaway invocations can exhaust account concurrency and starve other functions
Set reserved concurrency; use SQS with a DLQ as a buffer
Over-provisioned EC2 for bursty workloads
Paying for idle capacity 20h/day
Switch to Fargate + auto-scaling or Lambda for bursty traffic patterns
Gotchas
RDS encryption cannot be added after creation - You cannot enable encryption on an existing unencrypted RDS instance in place. The only path is to take a snapshot, copy it with encryption enabled, and restore to a new instance. Plan encryption at creation time for any instance that might hold regulated or sensitive data.
Lambda concurrency exhaustion is account-wide - Lambda functions share a per-region concurrency limit (default 1,000). A single runaway function (e.g., triggered by an SQS loop) can consume all available concurrency and throttle every other Lambda in the account. Always set reserved concurrency on high-traffic or loop-risky functions.
NAT Gateway costs accumulate silently - NAT Gateways charge per GB processed plus an hourly fee. A private subnet with heavy outbound traffic (e.g., Lambda pulling large S3 objects) can generate surprising bills. Use VPC endpoints for S3 and DynamoDB to bypass NAT Gateway entirely for those services.
S3 eventual consistency trap (pre-2020 style) - While S3 now provides strong read-after-write consistency for new objects, workflows that delete and recreate objects with the same key can still observe stale list results under some conditions. Don't assume a ListObjects immediately after a delete/recreate reflects the latest state in automated pipelines.
IAM policy evaluation order surprises - An explicit Deny anywhere in the evaluation chain (SCPs, permission boundaries, identity policies, resource policies) overrides any Allow. A service control policy at the organization level silently blocking an action is a common source of "permission denied" that looks correctly configured in the IAM console.
References
For detailed patterns and service-specific guidance, read the relevant file from
the references/ folder:
references/service-map.md - quick reference mapping use cases to AWS services
Only load a references file when the current task requires detailed service lookup -
they consume context and the SKILL.md covers the most common decisions.
Companion check
On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install:
