In our last session, we saw how cloud computing allows app usage without handling real hardware. Today begins understanding AWS fundamentals.
AWS Global Infrastructure
AWS runs on strong worldwide systems. That’s why apps work without issues. Wherever customers are located, speed stays high. From day one, delays stay low while uptime remains solid.
Regions and Availability Zones
- Regions are geographic areas such as US East (N. Virginia) or Asia Pacific (Mumbai).
- Each Region includes several Availability Zones (AZs), which are isolated data centers. Each data center has independent power, networking, and cooling.
We could lower the risk by spreading things across different regions and zones.
Edge Locations, Local Zones, and Wavelength
AWS offers local spots to speed up apps for people - using nearby sites helps performance while cutting delays across regions.
- Edge Locations: Cache content near users.
- Local Zones: Bring some AWS services closer to big cities.
- Wavelength Zones: Connect to 5G networks for very low-latency apps.
AWS Outposts
If you want AWS tools locally, Outposts brings the network into your facility - offering combined cloud access. Rather than keeping systems separate, it links internal operations with external resources seamlessly - using consistent management layers across both environments.
Shared Responsibility Model
Security on the cloud doesn't happen by itself. With the Shared Responsibility Model, AWS shows what parts each party must manage.
- AWS handles "Security of the Cloud": Protects the physical data centers, servers, networking, and foundational services.
- You handle "Security in the Cloud": Responsible for applications, data, identity, access controls, encryption, and network configurations.
It's a joint effort: AWS supplies the safe foundation, while you develop atop it with care.
AWS Well-Architected Framework
AWS offers a method known as the Well-Architected Framework. This approach supports creating stable, efficient systems. The model rests on six core areas. As stated in their public documentation, these elements include:
- Operational Excellence – Monitor and improve systems continuously.
- Security – Protect data, accounts, and workloads.
- Reliability – Recover quickly from failures.
- Performance Efficiency – Use resources smartly and scale efficiently.
- Cost Optimization – Avoid waste and maximize value.
- Sustainability – Reduce environmental impact.
Sticking to these principles enables the creation of safe, high-performing software that works consistently - using them streamlines your process while improving outcomes through better structure instead of guesswork.
Conclusion
Here, we looked at AWS global infrastructure, its shared responsibility approach - also exploring the well-architected guidelines from AWS.
Top comments (2)
thanks M. Oly ✨
🤍