For e-commerce
AWS cost optimisation for e-commerce companies
E-commerce infrastructure gets sized for the busiest hour of the year and then billed for all 8,760 of them. The seasonal peak is real; paying for it in February is not. Add years of product imagery and "temporary" copies of the production database, and the bill creeps far ahead of sales growth.
The free scan shows what your quiet-month baseline actually needs versus what it costs — before the next peak locks the sizing in for another year.
Run the free scanWhere e-commerce AWS bills leak
- →Peak-shaped everything. Instances scaled up for Black Friday and never scaled back down; databases sized for the January sale running at that size in June. If autoscaling only ever went up, the baseline is a monument to your best day.
- →Media storage without lifecycle. Every product image, in every size variant, for every product you have ever sold — in S3 Standard, forever. Delisted product media and old campaign assets belong in cheaper tiers or the bin; a lifecycle policy does it automatically.
- →Copies of the production database. Dev, staging and analytics each got a full prod copy "temporarily". Three extra multi-hundred-GB databases, running 24/7, months later. Subset data or schedule them off outside working hours.
- →Logs at retail volume. High-traffic stores generate serious CloudWatch ingestion — access logs, bot traffic, health checks — often at DEBUG verbosity nobody reads. At $0.50/GB ingested, noisy logging on a busy storefront is real money.
- →On-demand at steady-state. Even seasonal businesses have a steady floor — the baseline traffic outside peaks. That floor should be on Savings Plans; the peaks stay on-demand. Most accounts run 100% on-demand instead.
Put numbers on it
EC2 idle cost estimator
What your under-5%-CPU instances cost, and what rightsizing the quiet ones saves.
Open calculator →
Savings Plans calculator
On demand against one and three year commitments, and why rightsizing has to come first.
Open calculator →
CloudWatch Logs cost calculator
Log groups that never expire, plus $0.50 per GB to ingest. See what logging actually costs.
Open calculator →
Frequently asked questions
We need headroom for sales spikes. Doesn’t optimisation remove it?
No — the fix for peaks is elasticity (autoscaling that goes both directions), not permanent capacity. You commit to the steady floor, autoscale the spikes, and stop paying peak prices in the quiet months. Headroom you actually use is not waste; headroom running idle for eleven months is.
Our platform is Shopify but we run services on AWS. Worth auditing?
Those side accounts — image processing, ERP integrations, data pipelines, custom apps — are usually worse than pure-AWS shops, because they are nobody’s main job. Small account, high waste percentage is the standard finding.
£499 fixed. Free scan first. 20%+ found or it’s free.
The scan is read-only — a role you create and delete, no keys shared — and shows your estimated monthly saving before anyone talks about money.