AWS Global Infrastructure
contents :
-Regions -Availability Zones -Scope -Maintaining resiliency -Locations
Infrastructure, like data centers and networking connectivity, still exists as the foundation of every cloud application. In AWS, this physical infrastructure makes up the AWS Global Infrastructure, in the form of Regions and Availability Zones.
Regions :
Regions are geographic locations worldwide where AWS hosts its data centers. AWS Regions are named after the location where they reside. For example, in the United States, the Region in Northern Virginia is called the Northern Virginia Region, and the Region in Oregon is called the Oregon Region. AWS has Regions in Asia Pacific, China, Europe, the Middle East, North America, and South America. And we continue to expand to meet our customers' needs. Each AWS Region is associated with a geographical name and a Region code.
Here are examples of Region codes:
us-east-1 is the first Region created in the eastern US area. The geographical name for this Region is N. Virginia.
ap-northeast-1 is the first Region created in the northeast Asia Pacific area. The geographical name for this Region is Tokyo.
Choosing the right AWS Region
AWS Regions are independent from one another. Without explicit customer consent and authorization, data is not replicated from one Region to another. When you decide which AWS Region to host your applications and workloads, consider four main aspects: latency, price, service availability, and compliance.
Latency : If your application is sensitive to latency (the delay between a request for data and the response), choose a Region that is close to your user base. This helps prevent long wait times for your customers. Synchronous applications such as gaming, telephony, Web Sockets, and Internet of Things (IoT) are significantly affected by high latency. Asynchronous workloads, such as ecommerce applications, can also suffer from user connectivity delays.
Price : Due to the local economy and the physical nature of operating data centers, prices vary from one Region to another. Internet connectivity, imported equipment costs, customs, real estate, and other factors impact a Region's pricing. Instead of charging a flat rate worldwide, AWS charges based on the financial factors specific to each Region.
Availability : Some services might not be available in some Regions. The AWS documentation provides a table that shows the services available in each Region.
Compliance : Enterprise companies often must comply with regulations that require customer data to be stored in a specific geographic territory. If applicable, choose a Region that meets your compliance requirements.
Availability Zones
Inside every Region is a cluster of Availability Zones. An Availability Zone consists of one or more data centers with redundant power, networking, and connectivity. These data centers operate in discrete facilities in undisclosed locations. They are connected using redundant high-speed and low-latency links.
Availability Zones also have code names. Because they are located inside Regions, they can be addressed by appending a letter to the end of the Region code name. Here are examples of Availability Zone codes:
us-east-1a is an Availability Zone in us-east-1 (N. Virginia Region).
sa-east-1b is an Availability Zone in sa-east-1 (São Paulo Region).
Therefore, if you see that a resource exists in us-east-1c, you can infer that the resource is located in Availability Zone c of the us-east-1 Region.
Scope of AWS services
Depending on the AWS service that you use, your resources are either deployed at the Availability Zone, Region, or Global level. Each service is different, so you must understand how the scope of a service might affect your application architecture.
All you have to do to run a Region-scoped service is choose the Region you wish to use. The service is said to function on a region-scope level if you are not prompted to choose which specific availability zone to install it in. When it comes to Region-scoped services, AWS takes proactive measures to improve the durability and availability of data.
Maintaining resiliency
You need to maintain resilience and high availability in order to keep your application running. Using managed services that are region-scoped is a well-known best practice for cloud architecture. Resilience and availability are inherent features of these services. Make sure your workload is distributed throughout several Availability Zones if that isn't feasible. You ought to utilise two Availability Zones, at the very least. In this manner, your application will have infrastructure operational in a second Availability Zone to take over traffic in the event that one Availability Zone fails.
**Edge locations
**
Edge locations are global locations where content is cached. For example, if your media content is in London and you want to share video files with your customers in Sydney, you could have the videos cached in an edge location closest to Sydney. This would make it possible for your customers to access the cached videos more quickly than accessing them from London. Currently, there are over 400+ edge locations globally.