Week 3: Understanding AWS Global Infrastructure and Services
As I continue my AWS learning journey, Week 3 helped me understand what is happening behind the AWS Cloud. After learning about AWS pricing, billing, and cost management in Week 2, this module introduced me to the infrastructure that supports AWS services and how those services are organized.
Understanding the AWS Global Infrastructure
One of the main areas I explored this week was the AWS Global Infrastructure.
I learned that AWS infrastructure is built around Regions, Availability Zones, and Points of Presence, including edge locations. Understanding how these components work together helped me see how AWS provides reliable and scalable cloud services across different geographical locations.
AWS Regions
An AWS Region is a geographical location that contains multiple Availability Zones. I learned that Regions are isolated from one another, which means resources stored in one Region are not automatically replicated to another Region.
I also learned that choosing a Region is an important decision when deploying AWS resources. Factors such as data governance, legal requirements, latency, service availability, and cost can influence the choice of region.
For example, locating resources closer to users can help reduce latency and improve the user experience.
Availability Zones
I also learned about Availability Zones (AZs) and their role in building highly available applications.
Availability Zones are separate locations within an AWS Region, with independent infrastructure such as power and networking. They are connected through high-bandwidth, low-latency networking.
This showed me why applications should not depend on a single Availability Zone. By distributing resources across multiple Availability Zones, applications can be better protected against failures and remain available when problems occur in one location.
Data Centers and Edge Locations
The module also helped me understand the relationship between data centers and Availability Zones. Data centers provide the physical foundation for AWS infrastructure, while customers work with Availability Zones rather than selecting individual data centers.
I also learned about edge locations, which are part of AWS Points of Presence. Services such as Amazon CloudFront use edge locations to cache and deliver content closer to users, helping reduce latency.
This helped me understand that cloud performance is not only about where an application is hosted, but also about how content is delivered to users.
AWS Service Categories
Another major part of the module was learning how AWS services are organized into different service categories.
The categories introduced in the module included:
- Compute – services such as Amazon EC2, AWS Lambda, Amazon ECS, Amazon EKS, and AWS Fargate.
- Storage – services such as Amazon S3, Amazon EBS, Amazon EFS, and S3 Glacier.
- Database – services such as Amazon RDS, Amazon Aurora, Amazon Redshift, and Amazon DynamoDB.
- Networking and Content Delivery – services such as Amazon VPC, Elastic Load Balancing, Amazon CloudFront, Amazon Route 53, and AWS VPN.
- Security, Identity, and Compliance – services such as AWS IAM, AWS Organizations, Amazon Cognito, AWS KMS, and AWS Shield.
- Cost Management – services such as AWS Budgets, AWS Cost Explorer, and AWS Cost and Usage Reports.
- Management and Governance – services such as AWS Management Console, Amazon CloudWatch, AWS CloudTrail, AWS Config, and AWS Trusted Advisor.
I did not need to memorize every AWS service. Instead, I focused on understanding what the major service categories are and the purpose of some of the commonly used services within them.
Exploring the AWS Management Console
The module also included a hands-on activity where I explored the AWS Management Console.
This gave me the opportunity to become more familiar with the interface used to access and manage AWS services. It was useful to connect the concepts from the lessons with the actual AWS environment rather than learning only from theory.
What I Learned
The biggest lesson I took from this module is that understanding AWS requires more than knowing individual services.
I now have a better understanding of where AWS resources run, how AWS maintains availability, how content is delivered closer to users, and how different AWS services are grouped according to their functions.
Week 3 also helped me see how the different parts of AWS infrastructure support the services that users interact with. Regions and Availability Zones provide the foundation, while services for computing, storage, databases, networking, security, and management provide the tools needed to build cloud solutions.
As I continue my AWS learning journey, I look forward to moving from understanding the AWS environment to gaining more hands-on experience with the services themselves.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article