Free Local AWS Emulators in 2026: What Each One Runs and Where Each One Stops
LocalStack's free edition ended in March 2026, and on 11 November AWS shipped its own emulator. Where each local option runs, what it costs and where it stops.
This is Part 3 of our AWS Cost Optimization series. If you haven't read the earlier parts, start there:
You know where hidden costs hide. You know the strategies. Now you need a process.
This playbook is for DevOps engineers, platform teams, and engineering managers who can access AWS Cost Explorer and have permission to review (not necessarily change) infrastructure. You should be comfortable navigating the AWS console and understand basic concepts like EC2 instances, RDS, S3, and VPCs.
If you're a finance or operations lead without AWS access, partner with your engineering team to run this together.
| Account Size | Resources | Estimated Time |
|---|---|---|
| Small | <50 resources | 4-6 hours |
| Medium | 50-200 resources | 6-10 hours |
| Large | 200+ resources, multi-account | 2-3 days |
For multi-account setups (AWS Organizations), run the audit per account or use consolidated billing views. Aggregate findings in a shared spreadsheet. Prioritize accounts by spend. Audit the top 3 accounts by cost first.
This is the playbook we run with clients. Systematic. Repeatable. Actionable.
Run it once, find the obvious waste. Run it quarterly, cost optimization becomes routine.
30 minutes of setup saves hours later.
At minimum, you need read access to:
If you have Business or Enterprise support, get access to AWS Trusted Advisor too.
Enable AWS Compute Optimizer. It's free. It generates right-sizing recommendations automatically.
The ViewOnlyAccess managed policy covers most of what you need. For multi-account setups, configure cross-account access or use AWS Organizations.
Before deleting anything, check with your team:
Document these requirements before the audit. Every "delete this" recommendation in this playbook should be filtered through your compliance constraints first.
When in doubt, ask. Deleting data that compliance requires is worse than paying for storage you don't need.
Before optimizing, know where you stand:
Total monthly spend. Average the last 3 months. Write this number down.
Spend by service. Top 10 services by cost. Most accounts follow Pareto: a few services drive most spend.
Spend trend. Month-over-month change. Growing spend isn't bad if you know why.
Production vs non-production. If you tag by environment, pull this breakdown. Non-prod wastes more because nobody reviews it.
Tagging health check. If tagging is inconsistent or missing, note this as a finding. You can't optimize what you can't categorize. Consider prioritizing a tagging cleanup before or alongside this audit. At minimum, tag resources by: Environment (prod/staging/dev), Project or Application, and Owner (team or person).
Document these baselines before changing anything. You can't measure improvement without knowing your starting point.
2-3 hours for a thorough review.
Start with EC2. Usually the biggest cost driver. Usually the easiest to fix.
Open Compute Optimizer and review recommendations. It analyzes CloudWatch metrics and suggests right-sizing. Don't accept blindly. Treat each recommendation as a question worth investigating.
Look for:
For Lambda:
Storage costs accumulate quietly.
EBS volumes:
EBS snapshots:
aws ec2 describe-snapshots --owner-ids self --query 'Snapshots[?!VolumeId]'S3 buckets:
Tip: Enable S3 Storage Lens (free tier available) to see access patterns across all buckets.
Often the second-largest cost after compute.
RDS:
DynamoDB:
Easy to overlook. Often significant.
Data transfer:
NAT Gateways:
Elastic IPs:
Load balancers:
Reserved Instances:
Savings Plans:
Coverage gaps:
1-2 hours to organize findings.
Quick wins (under 1 hour, minimal risk):
Note: "Quick wins" still require compliance review. Fast to execute doesn't mean skip due diligence.
Low effort (1-4 hours, low risk):
Medium effort (1-2 days, coordination needed):
High effort (1+ weeks, planning required):
For each finding:
Monthly savings. Be specific. "Right-size web-server-1 from m5.xlarge to m5.large: $70/month."
Implementation effort. Hours. People involved. Change windows.
Risk level. What could go wrong? How reversible?
High impact, low effort = do first. High impact, high effort = plan next. Low impact, low effort = maybe. Low impact, high effort = skip.
Focus on high-impact, low-effort first. Don't let perfect block good.
For each item:
Convert findings into a timeline.
Estimate savings first. Use AWS Pricing Calculator or Cost Explorer's forecast to quantify expected savings before implementing. This helps prioritize and builds confidence.
Know your rollback path. Most changes are reversible, but know how:
Under an hour each. Minimal risk.
These changes often save hundreds per month.
Some planning required. Not major projects.
Larger optimizations. Coordination required.
Only purchase Savings Plans or Reserved Instances after you have:
Start with 1-year Compute Savings Plans covering 50-60% of your baseline. You can always add more. You can't undo a commitment.
One-time audits don't last. Build cost awareness into operations.
30 minutes monthly:
Every quarter, run a lighter version of Phase 2 (1-2 hours instead of 2-3):
The quarterly review focuses on changes since the last audit, not a full re-examination of everything. Your monitoring alerts should catch major issues between reviews.
Cost optimization is a practice, not a project.
The biggest savings come from building cost awareness into daily operations. Every infrastructure decision is a cost decision. When teams think about cost as they build, waste doesn't accumulate.
Start with quick wins. Build monitoring. Schedule reviews. Consistent attention beats any one-time cleanup.
The best cost optimization is prevention. Build cost awareness into your culture, not your quarterly fire drills.
This article is Part 3 of our AWS Cost Optimization series. Need help with your AWS cost audit? Contact us for a free initial assessment.