← All articlesInfra and cloud

A sample AWS bill, line by line

A bill built for the example, with real AWS prices. Nine lines, and four leaks I find in almost every account.

Julien Mauclair · ~4 min · intermediate
StackAWSEC2RDSFinOps

This bill is an example I built, not a client's bill. It uses a common architecture, priced with AWS public rates for the us-east-1 Region in November 2026: $569.05 a month. Reading it line by line, you find about $110 of waste, or 19%, which matches what Stralya finds in real accounts.

01The architecture in the example

A classic web application: two servers behind a load balancer, one background job server, a managed PostgreSQL database, a NAT gateway for outbound traffic, and disk backups. The servers are spread across two Availability Zones, as AWS recommends for high availability.

The maths uses 730 hours per month, AWS's convention for an average month.

02The bill, line by line

2 m5.large instances for the site, 2 × $0.096 × 730 h$140.16
1 m5.large instance for jobs, $0.096 × 730 h$70.08
RDS PostgreSQL db.t3.medium, $0.072 × 730 h$52.56
NAT gateway, $0.045 × 730 h plus 500 GB processed at $0.045$55.35
Data out to the internet, 1,100 GB with 100 free, at $0.09$90.00
Cross-zone transfer, 2,000 GB each way at $0.01$40.00
6 public IPv4 addresses, 6 × $0.005 × 730 h$21.90
EBS snapshots, 1,500 GB at $0.05$75.00
EBS gp3 volumes, 300 GB at $0.08$24.00
Monthly total$569.05

Prices come from AWS pages: m5.large instances and db.t3.medium database read on Vantage, which mirrors the AWS catalogue, NAT gateway and IPv4 addresses, data transfer, EBS storage and snapshots. In another Region, such as Paris, the amounts differ slightly, but the structure is the same.

03The four leaks hidden inside

No line looks wrong. That is exactly the problem. Here is what I check first.

Job instance at 10% CPU, replaceable by a t3.medium at $30.37$39.71
3 IPv4 addresses allocated but attached to nothing$10.95
800 GB of snapshots older than any useful retention$40.00
Half the cross-zone transfer, by moving the job server next to the database$20.00
Total recoverable$110.66

The t3.medium price, $0.0416 per hour, comes from the same source. A t3 is a burstable instance: it suits a workload that sits at 10% most of the time, not a sustained one.

In total, $110.66 out of $569.05, or 19% of the bill. These are the same families of leaks I describe in my article on AWS accounts: oversized instances, orphaned IPs, outdated backups, cross-zone transfer.

04What not to touch

Part of the bill looks expensive but does its job. The NAT gateway costs $55 a month in this example, but it lets private servers reach the internet without being exposed. You can sometimes shrink it, for example with VPC endpoints for AWS services, as I explain in the article on NAT gateway cost. Removing it without thinking breaks the application.

Likewise, keeping two web servers in two zones costs more than one, but that is what keeps the site up when a zone goes down. The goal is not the lowest bill, it is a bill where every line has a reason to exist.

05How to read your own bill

The method has three steps, and you can apply it to your own bill this month:

·open Cost Explorer and group by service, then by usage type;
·for each line above a few dollars, ask which part of the application it serves;
·for each resource, check its real utilisation before deciding anything.

Lines nobody can explain are almost always the first savings. My guide to cutting an AWS bill covers the next steps.

06FAQ

Why a sample bill rather than a real one?

Because a real bill belongs to a client and contains details they would not want published. The example uses a common architecture and public prices, so every calculation can be checked.

Is 19% waste realistic?

In the accounts Stralya audits, leaks of this kind add up to as much as 20% of the bill. The example was built to stay in that range.

Which line is most often oversized?

Compute instances. A machine picked for a peak or out of caution often runs at 10% of its capacity for months. It is also the line where dropping one size pays off most.

In short

An AWS bill is read line by line, asking what each one really serves. In this example, four questions are enough to find almost a fifth of the total.

Talk about your project ↗
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.

Read next