How to choose the Right Amazon AWS Region

Amazon AWS Cloud Infrastructure is built-in various locations called Regions across the world. Recently, Amazon AWS has launched a new Region in Frankfurt in EU Region. Recently, Amazon AWS has announced that another 5 AWS regions (and 11 Availability Zones) in Canada, China, India, Ohio, and the United Kingdom coming online throughout the next year. With this, Amazon AWS is having 10 public cloud Regions across the world. Other than this, AWS is having two different regions called AWS GOV Cloud (for US Government) and AWS China.

Amazon AWS is running most of the services as Region dependent like: EC2, RDS, SES, and CloudWatch etc and very few of the services are Region independent like: S3, Route53, CloudFront and IAM etc.

It would be hard for any Customer to choose the AWS Region to migrate and run their respective workloads on to the Cloud because of various AWS Regions. In this post, we will discuss few parameters to consider before choosing an AWS Region for your workloads.

Supported AWS Services

Most of the AWS Services and features are Region dependent and fewer services only Region independent. For example, SES and Workspaces will support only few of the AWS Regions. List out all the services you want to use it in Amazon AWS for your applications or workloads and make sure whether they are supported in the chosen Region. Please refer this URL to identify the list of all the AWS services and supported regions.

Service Level Agreements

Review all of the AWS Services SLAs which you are using for your workloads. Because all the AWS Services are not delivering the same kind of SLAs. Each service abide its own SLA. For Example, S3 gives the Monthly Uptime of atleast 99.9% whereas EC2 gives the Monthly Uptime of atleast 99.95%. These SLAs will be met by AWS if you deploy your application as per the AWS Design and Best practices.


The AWS Services cost will be different for each region, because the physical AWS infrastructure cost, taxes, man power and etc will be different for Region to Region. For example, m3.large ec2 instance cost in EU Frankfurt region is $119.52, whereas the same instance cost in US N.Virginia is $100.8. So review and compare the cost of the AWS regions which you have chosen to deploy your workloads. Amazon has Cost Calculator to create a glance of your monthly cost based on your inputs.


When any end user accessing your service or application, it should be blazing fast. So you need to identify the locations of the target audience or end users based on that you can choose the region which has less latency from your customer locations. CloudPing andCloudWatch websites will give you the latency of various AWS services of various AWS Regions from your browser. Apart from these, you should create a PoC on chosen AWS Region and perform the load testing and see how application is responding. Based on the latency results you can choose the AWS Region.

Security & Compliance

Applications related to the Health Care, Banking, Finance and Education sectors abide with the data Security and Compliance. Every Country has their own Security &Compliance rules when the customer data is moving from one location to the other location. If your application/customer data has any compliance requirements, please review the AWS services and their compliance certifications based on that you can choose whether we can run our workloads using that service or not? For example, Amazon RDS doesn’t have the HIPAA (Health Insurance Portability and Accountability) or FERPA (Family Educational Rights and Privacy) compliance certifications. In this case you can’t run your MySQL, Oracle, PostgreSQL and SQL Server workloads on RDS, rather you can choose the EC2 to run these applications where EC2 is HIPAA and FERPA compliance certified AWS service.

The above parameters will help you to review your requirements and choose the best suitable Region for your application hosting and deployment.

Leave a Comment

Your email address will not be published.

4 Trackbacks