what considerations are there when choosing which region to use? (choose 2)
The AWS Cloud is an ever-growing network of Regions and points of presence (PoP), with a global network infrastructure that connects them together. With such a vast selection of Regions, costs, and services available, information technology can be challenging for startups to select the optimal Region for a workload. This conclusion must exist made advisedly, as it has a major bear on on compliance, toll, functioning, and services bachelor for your workloads.
Evaluating Regions for deployment
There are iv principal factors that play into evaluating each AWS Region for a workload deployment:
- Compliance. If your workload contains data that is bound by local regulations, then selecting the Region that complies with the regulation overrides other evaluation factors. This applies to workloads that are bound past data residency laws where choosing an AWS Region located in that country is mandatory.
- Latency. A major factor to consider for user experience is latency. Reduced network latency tin can brand substantial touch on enhancing the user experience. Choosing an AWS Region with close proximity to your user base location can reach lower network latency. It can also increase communication quality, given that network packets take fewer exchange points to travel through.
- Toll. AWS services are priced differently from one Region to another. Some Regions take lower toll than others, which can result in a cost reduction for the same deployment.
- Services and features. Newer services and features are deployed to Regions gradually. Although all AWS Regions have the aforementioned service level understanding (SLA), some larger Regions are unremarkably offset to offer newer services, features, and software releases. Smaller Regions may not get these services or features in time for you to employ them to back up your workload.
Evaluating all these factors tin can brand coming to a decision complicated. This is where your priorities as a business should influence the decision.
Assess potential Regions for the right pick
Evaluate by shortlisting potential Regions.
- Check if these Regions are compliant and have the services and features you need to run your workload using the AWS Regional Services website.
- Check feature availability of each service and versions available, if your workload has specific requirements.
- Calculate the toll of the workload on each Region using the AWS Pricing Calculator.
- Exam the network latency betwixt your user base location and each AWS Region.
At this indicate, you should have a listing of AWS Regions with varying price and network latency that looks something Tabular array 1:
| Region | Compliance | Latency | Cost | Services / Features |
|---|---|---|---|---|
| Region A | ✓ | 15 ms | $$ | ✓ |
| Region B | ✓ | 20 ms | $$$ | X |
| Region C | ✓ | 80 ms | $ | ✓ |
Table 1. Region evaluation matrix
Many workloads such as high performance calculating (HPC), analytics, and auto learning (ML), are not directly linked to a customer-facing application. These would not be sensitive to network latency, so yous may desire to select the Region with the lowest cost.
Alternatively, you may have a backend service for a game or mobile awarding in which network latency has a straight impact on user experience. Measure out the departure in network latency betwixt each Region, and make up one's mind if it is worth the increased cost. You can leverage the Amazon CloudFront edge network, which helps reduce latency and increases communication quality. This is because it uses a fully managed AWS network infrastructure, which connects your application to the edge location nearest to your users.
Multi-Region deployment
Y'all can likewise split up the workload across multiple Regions. The same workload may accept some components that are sensitive to network latency and some that are not. You may determine you lot tin can benefit from both lower network latency and reduced cost at the same fourth dimension. Hither's an example:
Effigy ane. Multi-Region deployment optimized for feature availability
Figure 1 shows a serverless application deployed at the Bahrain Region (me-south-1) which has a close proximity to the client base of operations in Riyadh, Saudi Arabia. Application users savor a lower latency network connecting to the AWS Deject. Analytics workloads are deployed in the Ireland Region (eu-west-i), which has a lower cost for Amazon Redshift and other features.
Note that data transfer between Regions is not free and, in this case, costs $0.115 per GB. Notwithstanding, even with this additional cost factored in, running the analytical workload in Ireland (eu-west-1) is yet more price-constructive. You tin can also benefit from boosted capabilities and features that may have not yet been released in the Bahrain (me-southward-one) Region.
This multi-Region setup could as well be beneficial for applications with a global user base. The application can be deployed in multiple secondary AWS Regions closer to the user base locations. Information technology uses a main AWS Region with a lower price for consolidated services and latency-insensitive workloads.
Figure 2. Multi-Region deployment optimized for network latency
Figure 2 allows for an application to span multiple Regions to serve read requests with the everyman network latency possible. Each customer volition be routed to the nearest AWS Region. For read requests, an Amazon Route 53 latency routing policy will be used. For write requests, an endpoint routed to the primary Region will be used. This primary endpoint can also have periodic wellness checks to failover to a secondary Region for disaster recovery (DR).
Other factors may also apply for certain applications such as ones that require Amazon EC2 Spot Instances. Regions differ in size, with some having three, and others upwardly to six Availability Zones (AZ). This results in varying Spot Case chapters available for Amazon EC2. Choosing larger Regions offers larger Spot chapters. A multi-Region deployment offers the most Spot capacity.
Conclusion
Selecting the optimal AWS Region is an important first stride when deploying new workloads. In that location are many other scenarios in which splitting the workload across multiple AWS Regions tin can result in a ameliorate user feel and cost reduction. The four factors mentioned in this blog mail can be evaluated together to discover the near appropriate Region to deploy your workloads.
If the workload is jump by whatever regulations, shortlist the Regions that are compliant. Mensurate the network latency betwixt each Region and the location of the user base. Estimate the workload cost for each Region. Cheque that the shortlisted Regions accept the services and features your workload requires. And finally, determine if your workload can do good from running in multiple Regions.
Swoop deeper into the AWS Global Infrastructure Website for more information.
thurgoodwhoultall69.blogspot.com
Source: https://aws.amazon.com/blogs/architecture/what-to-consider-when-selecting-a-region-for-your-workloads/