Five AWS Cost Optimisation Checks We Run Before Touching Anything Else
Most AWS bills we review have the same handful of easy savings sitting in them, unnoticed for months.
When we take on a client already running AWS infrastructure, cost review is usually the first exercise, and it's rarely a difficult one, since the same few patterns turn up in most accounts we look at.
Unattached EBS volumes, storage left behind after an EC2 instance was terminated but never actually deleted, are the single most common finding. They cost money every month for literally nothing.
Oversized instances running well below their provisioned capacity are the second: an instance sized for a launch-day traffic spike, still running at that size a year later. Right-sizing based on actual CloudWatch utilisation data routinely finds real, immediate savings.
The other three: reserved instances or savings plans not yet purchased for genuinely stable, predictable workloads; old snapshots never cleaned up; and data transfer costs from architecture that routes traffic less efficiently than it needs to between regions or availability zones.
None of these require re-architecting anything. They're a housekeeping pass, and they're worth doing on a schedule, quarterly at minimum, rather than only when a bill spikes unexpectedly and someone finally goes looking.
