Most expensive AWS bills I review are not caused by one big mistake. They come from defaults that nobody questioned: a NAT Gateway in the data path, microservices that talk across Availability Zones, batch jobs kept On-Demand, a DynamoDB table provisioned to hide a hot key.

I priced four of them with AWS list prices (checked on 18 November 2026) for Europe (Paris, Frankfurt), the Middle East (UAE, Bahrain) and US East (N. Virginia) as a reference.

1. S3 traffic going through a NAT Gateway

Private workloads that read from S3 through a NAT Gateway pay NAT data processing on every gigabyte:

Region NAT data processing
Europe (Paris) $0.05 / GB
Europe (Frankfurt) $0.052 / GB
Middle East (UAE) $0.0528 / GB
Middle East (Bahrain) $0.0528 / GB
US East (N. Virginia) $0.045 / GB

At 100 TB a month that is about $5,000 in Paris and $5,280 in the UAE.

Fix: an S3 gateway endpoint, which AWS provides at no additional charge, plus one route in the private route tables.

2. Microservices talking across Availability Zones

Data transfer between Availability Zones in the same Region is billed $0.01/GB in each direction. With 500 TB a month of internal traffic spread evenly over three zones, about two thirds crosses a zone boundary: roughly $6,700 a month.

Fix: keep calls inside the zone when possible. In Kubernetes, trafficDistribution: PreferSameZone on the Service (PreferClose is the older name). Keeping 80% of calls in-zone saves about $5,300 a month in this example.

Note: if your design relies on AWS App Mesh, it reached end of support on 30 September 2026.

3. Stateful batch jobs kept On-Demand

Region m5.2xlarge On-Demand (Linux) Lowest Spot price
Europe (Paris) $0.448/h $0.1486/h
Europe (Frankfurt) $0.46/h $0.1803/h
Middle East (UAE) $0.471/h $0.1997/h
Middle East (Bahrain) $0.471/h $0.1692/h
US East (N. Virginia) $0.384/h $0.1612/h

100 instances running all month in Paris: $32,704 On-Demand. Moving 90% of the hours to Spot, with job state checkpointed to EBS or S3 and an EventBridge rule on the two-minute interruption notice, brings it to about $13,000. Spot prices change by zone and over time, and capacity is not guaranteed, so keep an On-Demand fallback.

4. A DynamoDB hot partition

A single partition accepts at most 1,000 write units per second. Over-provisioning the table does not fix a hot key: the extra capacity is spread over partitions that are not under pressure. Write sharding (a random or calculated suffix on the key) spreads the load, and you only pay for the capacity you need.

Provisioned write capacity costs $0.000772 per WCU-hour in Paris, $0.0008085 in the UAE and Bahrain, and $0.00065 in N. Virginia.

The regional gap

The same architecture does not cost the same everywhere. Compared with N. Virginia, On-Demand m5.2xlarge is about 17% more expensive in Paris, 20% in Frankfurt and 23% in the UAE and Bahrain. That is not a reason to leave your Region (latency, data residency and customers decide that), but it is a reason to fix the defaults first.

Try it with your own numbers

I put the four scenarios in a free calculator: pick a Region, enter your own volumes, and see the default cost, the optimised cost and the trade-offs: AWS cost scenarios calculator

Prices are public list prices, excluding tax and discounts (Savings Plans, Reserved Instances, private pricing). Always confirm against your own Cost and Usage Report.

Mohamed Ali Dridi, electromechanical and IT engineer, founder of Koyotec Engineering (Tunis), Registered AWS Partner.

Sources