01
AWS bill review
Review your Cost and Usage Report and read-only IAM access across AWS Organizations accounts. Break down spend by service, linked account, and environment, and flag missing cost-allocation tags.
Services
01
Review your Cost and Usage Report and read-only IAM access across AWS Organizations accounts. Break down spend by service, linked account, and environment, and flag missing cost-allocation tags.
02
Check for idle EC2, oversized RDS, unattached EBS volumes, old snapshots, NAT Gateway charges, and inter-AZ or inter-region data transfer. Compare cost changes with usage so normal growth is not mistaken for waste.
03
Receive a findings list with estimated monthly savings, the calculation assumptions, implementation effort, operational risks, and a proposed owner. Review quick wins separately from changes that need testing.
04
Help your engineers assess EC2 and RDS rightsizing, Graviton migration, Instance Scheduler for non-production, S3 lifecycle and Intelligent-Tiering, and Savings Plans or Reserved Instance coverage. Your team approves and controls changes; performance and availability come before cost reduction.
05
Compare post-change billing and usage with the agreed baseline. Separate estimated opportunities from realized savings, account for workload changes, and revisit findings at a review cadence agreed with your team.
Ask CloudCurbs
A human will follow up
Tell us what’s happening with your AWS bill and how we can reach you.