DAY 10 : 🌐 AWS Infrastructure Demystified: From Regions to Edge Locations
"I'm a 3rd-year Computer Engineering student at Marwadi University with skills in C++, web development (MERN stack), and DevOps tools like Kubernetes. I contribute to open-source projects and share tech knowledge on GitHub and LinkedIn. I'm learning cloud technologies and app deployment. As an Internshala Student Partner, I help others find jobs and courses." now currently focusing on #90DaysOfDevops
Technology Deployment Methods:
AWS Console Web GUI:
Suitable for users who prefer a visual representation of their infrastructure.
Ideal for monitoring logs, alerts, and metrics with graphical presentations.
Involves extensive navigation and clicking due to numerous menus.
AWS CLI (Command Line Interface):
Preferred by engineers who are comfortable with command-line operations.
Facilitates easy management of resources with commands that can be copied and pasted.
Some resource settings can only be adjusted via the CLI.
AWS SDK (Software Development Kit):
Provides APIs in various programming languages for managing and interacting with AWS.
Enables applications to create resources within AWS.
Global Infrastructure:
Regions:
Geographical locations where AWS services can be deployed.
Not all services are available in every region, and pricing may vary.
Availability Zones (AZ):
- Independent and isolated data centers within regions.
Edge Locations:
Smaller points of presence globally to reduce latency by bringing services closer to end-users.
Limited services are available, primarily used for CDN (Content Delivery Network) services like CloudFront, Route 53, and AWS WAF.
Local Zones:
Extensions of AWS regions located near users in specific metropolitan areas.
Feature isolated infrastructure connected to parent regions via high-bandwidth links.
Offer a subset of services such as EC2 and EBS.
Thankyou for reading !!!!!!
