AWS bill shock

AWS Bill Shock Decisions

Use these pages when an AWS bill feels wrong and the team is not sure whether the answer is cleanup, architecture change, or leaving AWS.

AWS vs Smaller Cloud For Simple Workloads: When Default Cloud Is Too Muchcomparison

A practical decision page for deciding when a simple workload should stay on AWS or move to a smaller cloud, managed platform, or bare metal.

 S3 Cost Surprise: Storage Is Only Part Of The AWS Billcost_breakdown

A practical S3 cost breakdown covering storage, requests, retrieval, replication, lifecycle rules, and data transfer surprises.

 CloudWatch Cost Surprise: Logs, Metrics, And The Observability Taxcost_breakdown

A practical AWS CloudWatch cost breakdown for logs, metrics, retention, dashboards, and workload observability tradeoffs.

 AWS Data Transfer Cost Confusion: Egress, Cross-AZ, And Region Mistakescost_breakdown

A practical page for understanding AWS data transfer cost surprises across egress, cross-AZ traffic, regions, and workload placement.

 AWS NAT Gateway Surprise Bills: When Private Subnet Traffic Gets Expensivecost_breakdown

A practical decision page for understanding AWS NAT Gateway cost surprises and when architecture, endpoints, or placement may need review.

 Why Is My AWS Bill So High? The Usual Places To Look Firstcost_breakdown

A practical AWS bill shock checklist for finding common cost drivers before moving workloads or blaming EC2.

RunPlacement quiz

Pressure-test this workload

Find the top bill drivers before deciding whether AWS is the wrong placement.

Uses workload type, budget, GPU need, data movement, priority, and ops tolerance.
Use the quiz