Cloudhopper
Comparative Analysis

Hidden Costs in the Serverless Cloud (5): Regions

, 7 min read

26 % more for the same logs in Frankfurt than in N. Virginia, at the same Lambda price

Most cloud prices depend on the region, and it is tempting to assume that picking a cheaper region is an easy way to save. For AWS Lambda itself, that is rarely true. For the services around it, it can be.

This is the fifth article in our series on the costs that serverless cost estimates leave out, after the free tier, data transfer, logging and API Gateway.

What Lambda costs where

We compared the list prices of all 36 regions in our price list on November 22, 2026. Compared with US East (N. Virginia), the price per GB-second and per request is:

Compared with N. Virginia Regions
10 % lower Malaysia, Taipei, Thailand
the same 24 regions, including all US regions, Frankfurt, Ireland, London, Paris, Stockholm, Spain, Tokyo, Sydney, Singapore, Mumbai, Canada and São Paulo
5 % higher New Zealand, Mexico, Tel Aviv
10 % higher Zurich
17 % higher Milan
24 % higher UAE, Bahrain
33 % higher Cape Town
38 % higher Hong Kong

In Europe, all the large regions cost the same. Only Zurich and Milan are more expensive.

Where the region does make a difference: logs

Log ingestion into CloudWatch is priced per region too, and there the differences are larger: $0.50 per GB in N. Virginia, Ohio and Oregon, $0.57 in Ireland, $0.63 in Frankfurt, $0.76 in Tokyo and $0.90 in São Paulo.

The API function from the last two articles shows what that means: 10 million requests a month of 100 ms at 512 MB, and 23 GB of logs at the INFO level. Its Lambda cost is the same in Frankfurt and N. Virginia, but its logs cost 26 % more in Frankfurt. In São Paulo, where Lambda also costs the same, the function with its logs comes to $31.03 a month, almost as much as in Hong Kong, the most expensive Lambda region:

Compute and requestsLog ingestion$0$10$20$30ThailandThailand, compute and requests: $9.30Thailand, log ingestion: $11.50$20.80 · logs $11.50N. VirginiaN. Virginia, compute and requests: $10.33N. Virginia, log ingestion: $11.50$21.83 · logs $11.50OregonOregon, compute and requests: $10.33Oregon, log ingestion: $11.50$21.83 · logs $11.50StockholmStockholm, compute and requests: $10.33Stockholm, log ingestion: $12.42$22.75 · logs $12.42IrelandIreland, compute and requests: $10.33Ireland, log ingestion: $13.11$23.44 · logs $13.11LondonLondon, compute and requests: $10.33London, log ingestion: $13.77$24.10 · logs $13.77FrankfurtFrankfurt, compute and requests: $10.33Frankfurt, log ingestion: $14.49$24.82 · logs $14.49MilanMilan, compute and requests: $12.06Milan, log ingestion: $13.80$25.86 · logs $13.80ZurichZurich, compute and requests: $11.37Zurich, log ingestion: $15.87$27.24 · logs $15.87BahrainBahrain, compute and requests: $12.83Bahrain, log ingestion: $14.49$27.32 · logs $14.49TokyoTokyo, compute and requests: $10.33Tokyo, log ingestion: $17.48$27.81 · logs $17.48Cape TownCape Town, compute and requests: $13.75Cape Town, log ingestion: $15.59$29.34 · logs $15.59São PauloSão Paulo, compute and requests: $10.33São Paulo, log ingestion: $20.70$31.03 · logs $20.70Hong KongHong Kong, compute and requests: $14.26Hong Kong, log ingestion: $18.40$32.66 · logs $18.40
The API function from parts 3 and 4 per month in 14 of the 36 AWS regions: 10 million requests of 100 ms at 512 MB on x86, and 23 GB of logs. List prices, November 22, 2026.

Other prices around the functions vary too. An API Gateway REST API costs $3.50 per million requests in N. Virginia and $3.70 in Frankfurt; an HTTP API $1.00 and $1.20. Log storage costs $0.03 per GB and month in N. Virginia and $0.0324 in Frankfurt. The Lambda free tier, by contrast, applies once per account across all regions.

Should you move to a cheaper region?

Usually not, and rarely for the Lambda price alone:

  • Where data may be stored is often decided by law or by contracts with customers. A European company with personal data has good reasons to stay in an EU region.
  • Latency to users and to the databases and services a function calls matters more than a few percent of the Lambda bill. A function in another region than its database pays with every request.
  • Data transfer between regions is billed per GB. Functions that read their data from another region pay for it on top, as described in the second article.
  • Moving is a project: functions, their triggers, databases, queues, permissions and monitoring all have to move together.

Where the region does pay off:

  • For new workloads, choose among the regions that are close to your users and allowed for your data. In Europe, that is usually a choice between equally priced regions anyway.
  • For functions in an expensive log region, reduce the logs before thinking about moving. The three settings from part 3 save more than a move would, and take minutes instead of weeks.
  • In the few expensive regions, such as Hong Kong, Cape Town or the Middle East, the difference of a quarter to a third can be worth a look for workloads that don’t depend on being there.

Summary

For AWS Lambda, the region matters less than many expect: 24 of 36 regions charge the same. The difference shows up in the logs, which cost up to 80 % more in some regions than in others, and in a handful of regions where everything is more expensive. Before moving functions, reduce their logs.

The Cloudhopper app prices every function at the list prices of its own region, including its logs, and recommends the log level, log class and retention that pay off. Its comparison with Google Cloud and Azure also uses the region closest to the function’s.


Contact Us