AWS bills rarely jump overnight. They creep: a test server nobody turned off, snapshots that pile up, a database sized for a launch that never needed it. Here is where we usually find the money.
Compute
- Idle instances. EC2 servers running 24/7 that are only used during business hours. Scheduling them off nights and weekends cuts their cost by roughly two-thirds.
- Oversized instances. CPU averaging 5% on a large instance. AWS Compute Optimizer will suggest smaller sizes.
- Old instance generations. Newer generations (including Graviton) usually give more performance per dollar.
- On-demand pricing for steady workloads. Savings Plans and Reserved Instances discount steady usage significantly; AWS quotes savings of up to 72% compared with on-demand.
Storage
- Unattached EBS volumes left behind when instances were deleted. They bill every month until removed.
- Snapshot sprawl. Years of daily snapshots with no lifecycle policy.
- gp2 volumes. Moving to gp3 is typically about 20% cheaper per GB with equal or better baseline performance.
- S3 in the wrong class. Rarely accessed data sitting in S3 Standard. Lifecycle rules can move it to cheaper tiers automatically.
Networking and logging
- Public IPv4 addresses. Since February 2024, AWS charges for every public IPv4 address, attached or not. Unused Elastic IPs are pure waste.
- NAT gateways and log retention. NAT gateways charge per hour and per GB processed, and CloudWatch log groups default to keeping logs forever. Both quietly grow.
Do not forget security while you are in there
The same review usually finds a root account without MFA, shared IAM users and security groups open to the whole internet. Fixing those costs nothing and closes the doors attackers look for.
Send us the bill: our free AWS bill review goes through every line with read-only access.