I do not want my AWS bill to bankrupt me

I do not want my AWS bill to bankrupt me. Please review my AWS account end-to-end
and address the following, explaining each change as you make it:

BILLING & ALERTS
- Set up billing alerts
- Add a monthly budget cap
- Check my Free Tier usage and flag anything about to exceed it

UNUSED RESOURCES
- Find unused resources across every region
- Identify orphaned EBS volumes and confirm with me before deleting them
- Check for idle EC2 instances

COMPUTE & SCALING
- Right size my instances based on actual usage, not peak capacity
- Enable upper limits on every Auto Scaling group
- Add a CDN (CloudFront) to cut bandwidth costs where it makes sense

STORAGE & DATABASE
- Check my S3 storage lifecycle rules and move cold data to cheaper tiers
- Review my database instance tier against actual load

NETWORK & TRAFFIC
- Find unattached Elastic IP addresses
- Review my CloudWatch Logs retention settings
- Cache expensive, repeated queries
- Check my data egress traffic and where it's coming from

PRICING STRATEGY
- Compare Reserved Instances and Savings Plans against my current On-Demand spend
- Check for regional pricing differences on resources I could safely move
- Flag any other risk or waste you notice, even if it wasn't listed above

Go resource by resource, explain what you changed and why, and flag anything you're
not fully confident fixing automatically so I can review it manually.

Most important: make no mistakes.

Why each section actually matters

• Billing & alerts: without a budget alert, a misconfigured Lambda loop or a public S3 bucket can run up thousands before anyone notices. AWS won't stop spending on its own.
• Unused resources: unattached volumes, idle load balancers and forgotten dev instances cost money every hour, whether or not anything uses them.
• Compute & scaling: an oversized instance and an Auto Scaling group with no upper limit are two of the most common ways a bill quietly doubles.
• Storage & database: data sitting in an expensive storage tier, or a database sized for peak load it never sees, adds up fast over months.
• Network & traffic: data egress is one of the least visible AWS costs. It doesn't show up until the bill does.
• Pricing strategy: On-Demand is the most expensive way to run anything long-term. Reserved Instances or Savings Plans can cut a steady workload by a large margin.

How to actually run it

1. Read-only first. Use an IAM role with read-only access for the first pass. Nothing gets deleted or resized until you've reviewed the findings yourself.
2. Snapshot before you touch anything. Before deleting a volume or resizing an instance, confirm a snapshot or backup exists.
3. One account, one region at a time. Don't point it at your whole AWS Organization in one pass. You'll get shallower checks and a much bigger blast radius if something goes wrong.
4. Confirm every deletion by hand. Never let an automated pass delete or terminate a resource without you personally confirming it's actually unused.
5. Re-run it monthly. Idle resources and the pricing tiers that make sense for you change as your usage changes.

Go deeper: follow-up prompts

Send these one at a time, after the first pass lands.

Write a COST-REPORT.md summarizing what you found and changed, with the estimated monthly savings for each item.

Set up a CloudWatch alarm that pages me if daily spend jumps more than 20% above the 7-day average.

Which three changes would save the most money with the least risk? Rank them.

One honest caveat. This catches the obvious waste fast: unused resources, missing budgets, oversized instances. It won't replace a proper FinOps review for a large, multi-account setup, and it should never touch a delete or resize action without your explicit confirmation first. Treat every suggested change as a proposal, not an instruction to execute blindly.