Understanding basic AWS cloud Architecture.

Dear Reader,

If you are reading this blog I assume that you are already jumped into the Cloud and DevOps role, but but DevOps or Cloud is not only about learning different tools, its majorly about a mindset, a mindset of understanding the error, understanding the architecture, understanding of architecture will always help you solve the issue in faster.

So, let’s understand How is AWS global infrastructure is Organized?

AWS infrastructure is majorly divided into :

1. Data Centers : Data Centers are the physical locations that stores computing machines and related hardware equipment, means data centers are those places with are majorly built for managing our AWS servers that are protected from any type of disasters either man-made or natural.

Now lets talk about Availability zone, when performing the hands-on you will come across numerous of time across Availability zone, so understanding it very important.

2. Availability Zone : A group of one or more data centers is called an Availability Zone.

   An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. When you launch an instance, you can choose an Availability Zone or let AWS choose one for you. If you distribute your instances across multiple Availability Zones and one instance fails, you can design your application so that an instance in another Availability Zone can handle requests.

   We will talk about Instances in different blog.

3. Regions : Each AWS Region consists of multiple isolated and physically separate Availability Zones within a geographic area.

   There are 117 Availability Zones within 37 Geographic Regions, with announced plans for 13 more Availability Zones and 4 more AWS Regions in New Zealand, the Kingdom of Saudi Arabia, Chile, and the AWS European Sovereign Cloud.

   whenever selecting the Region make sure to keep few points in mind it may vary region to region

   1. Governance and legal requirements – Consider any legal requirements based on data governance, sovereignty, or privacy laws.

   2. Latency – Close proximity to customers means better performance.

   3. Service availability – Not all AWS services are available in all Regions.

   4. Cost – Different Regions have different costs. Research the pricing for the services that you plan to use and compare costs to make the best decision for your workloads.

4. Local Zones: AWS Local Zones are a type of AWS infrastructure that places compute, storage, database, and other select AWS resources closer to large population and industry centers. This proximity allows users to run latency-sensitive applications and meet data residency requirements more effectively.

   Key Benefits of Local Zones

   Low Latency Applications

   AWS Local Zones enable the deployment of applications that require single-digit millisecond latency or local data processing. This is particularly useful for real-time gaming, live streaming, augmented and virtual reality (AR/VR), virtual workstations, and more.

   Data Residency

   AWS Local Zones help meet stringent data residency requirements by allowing data to remain in a specific country, state, or municipality. This is crucial for industries such as healthcare, financial services, and iGaming, where regulatory compliance is essential.

   Hybrid Cloud Migrations

   AWS Local Zones simplify hybrid cloud migrations by allowing segments of applications to be migrated to a nearby AWS Local Zone. This ensures low-latency requirements are met during the transition period until a full migration is possible.

And at the last we have

5. Edge Locations: An edge location is the nearest point to a requester of an AWS service. Edge locations are in major cities around the world. They receive requests and cache copies of your content for faster delivery. To deliver content to end users with lower latency, you use a global network of edge locations that support AWS services.

One common use for edge locations is to serve content closer to your customers.

This was the first and the basic architecture of AWS that you should know before jumping to different services of AWS.

Stay Tuned - Happy Learning.

LinkedIn