AWS Prices
Country Manager, India
AI, Manufacturing, DevOps, and Managed Services. 17+ years across Manufacturing, E-commerce, Retail, NBFC & Banking
With the AWS Stockholm region eu-north-1 launched I wanted to take a quick peek at the pricing. There have been rumors that the Stockholm region would be priced lower than many others so let’s compare.
I compared Stockholm to N. Virginia, Frankfurt and Ireland with EC2, Aurora, S3 and DynamoDB. Below is the pricing for each per region and the difference compared to Stockholm.
AWS Price Comparison
AWS EC2 Instance prices
AWS Region EU (Stockholm) – m5.2xlarge $0.408 per hour
AWS US East (N. Virginia) – m5.2xlarge $0.384 per hour -6%
AWS EU (Frankfurt) – m5.2xlarge $0.46 per hour +13%
AWS EU (Ireland) – m5.2xlarge $0.428 per hour +5%
AWS Amazon Aurora prices
(Note that I compare r5 to r4)
AWS EU (Stockholm) – db.r5.2xlarge $1.20 per hour
AWS US East (N. Virginia)- db.r4.2xlarge $1.16 per hour -3%
EU (Frankfurt)- db.r4.2xlarge $1.40 per hour +17%
Need expert help with aws prices?
Our cloud architects can help you with aws prices — from strategy to implementation. Book a free 30-minute advisory call with no obligation.
EU (Ireland) – db.r4.2xlarge $1.28 per hour +7%
AWS Amazon S3 Standard Storage prices
EU (Stockholm) – First 50 TB / Month $0.023 per GB
US East (N. Virginia) – First 50 TB / Month $0.023 per GB
EU (Frankfurt) – First 50 TB / Month $0.0245 per GB +7%
EU (Ireland) – First 50 TB / Month $0.023 per GB
AWS Amazon DynamoDB On-demand prices
EU (Stockholm) – Write request units $1.343 per million write request units
US East (N. Virginia) – Write request units $1.25 per million write request units -7%
EU (Frankfurt) – Write request units $1.525 per million write request units +14%
EU (Ireland) – Write request units $1.414 per million write request units +5%
Failure modes and rate of failure
Even though this all started with latency injection as in Yan Cui’s articles, latency is far from the only possible failure we can have in our serverless applications. In failure-lambda, failure-azurefunctions and failure-cloudfunctions there are now five different failure modes to choose from:
Identify Weaknesses
Injects latency to the executed function, controlled using a minimum and maximum span of milliseconds. This can for example be used to simulate service latency or to test and help set your timeout values.
Exception
Throws an exception in the function. Helps you test how your application and code handles exceptions.
Status code
Your function will return a status code of choice, for instance 502 or 404 instead of the normal 200. This gives you the possibility to test what happens when there are errors.
Disk space
Will fill your temporary disk with files to create a failure. If you’re using disk to store temporary files you can test how your application behaves if that disk gets full or you are unable to store to it.
Blacklist (courtesy of Jason Barto)
Blocks connections to specified hosts. Use to simulate services or third parties being unavailable.
All these failure modes can be used together with a rate of failure that you set. The default is to inject failure on every invocation but in reality, it is likely that for example a third party is unavailable on 50% of the calls made to that host or that an exception is thrown on a quarter of the invocations. Setting rate will allow you to achieve this.
For hands-on delivery in India, see managed AWS for Mumbai-region workloads.
About the Author
Country Manager, India at Opsio
AI, Manufacturing, DevOps, and Managed Services. 17+ years across Manufacturing, E-commerce, Retail, NBFC & Banking
Editorial standards: This article was written by a certified practitioner and peer-reviewed by our engineering team. We update content quarterly to ensure technical accuracy. Opsio maintains editorial independence — we recommend solutions based on technical merit, not commercial relationships.