AWS Certification – General Awareness & Current Affairs
“Basics” – Advanced University‑Level Study Notes
Audience – Students preparing for the AWS Certified Cloud Practitioner exam and those wishing to deepen their strategic understanding of AWS fundamentals.
Goal – Provide a rigorous, theory‑driven overview of the AWS ecosystem, its underlying principles, edge‑case scenarios, and a challenging problem to test mastery.
1. Introduction
AWS (Amazon Web Services) is the largest public cloud provider, offering >200 fully‑featured services. Its dominance stems from a combination of:
- First‑mover advantage – launched in 2006, it set the industry standard for cloud services.
- Extensive global infrastructure – 31 regions (2026) with 100+ Availability Zones (AZs) and 400+ edge locations.
- Ecosystem maturity – a vibrant partner network, an extensive set of developer tools, and a mature marketplace.
- Continuous innovation – 12–15 new services per year, often addressing emerging paradigms (serverless, AI/ML, edge).
The basics are the foundation for all advanced AWS knowledge. They encompass the cloud computing model, core services, global architecture, security & compliance, and operational practices.
2. Cloud Computing Fundamentals
| Term | Definition | Key AWS Example | Theoretical Insight |
|---|---|---|---|
| IaaS | Infrastructure as a Service – raw compute, networking, storage. | EC2, EBS, VPC | Enables a virtual data‑center, decoupling OS/VM from the underlying hardware. |
| PaaS | Platform as a Service – managed runtime environments. | Elastic Beanstalk, RDS, Lambda | Abstracts OS & middleware, letting developers focus on code. |
| SaaS | Software as a Service – fully‑hosted applications. | Amazon WorkSpaces, Amazon Chime | Eliminates software installation and maintenance. |
| Multi‑tenancy | Isolated workloads on shared physical resources. | All AWS services | Virtualization (hypervisor) + IAM + VPC isolation. |
| Elasticity | Dynamic resource scaling. | Auto Scaling, AWS Lambda | Allows cost‑efficient workload provisioning. |
| Pay‑as‑You‑Go | Consumption‑based pricing. | All AWS services | Monetization based on actual usage, encouraging lean architectures. |
2.1. Virtualization vs. Containerization
| Feature | Virtualization | Containerization |
|---|---|---|
| Isolation | Full OS per VM | Shared OS kernel, isolated namespaces |
| Overhead | High (hypervisor + OS) | Low (runtime + OS kernel) |
| Startup | Seconds | Milliseconds |
| Use‑case | Heterogeneous OS, legacy workloads | Micro‑services, rapid deployment |
Why containers matter: With the rise of container‑native services (ECS, EKS), AWS offers a managed Kubernetes‑compatible environment that leverages the same underlying AMIs and security controls as EC2.
2.2. Consistency & CAP Theorem in AWS
| Service | Consistency Model | CAP Classification | Practical Implication |
|---|---|---|---|
| DynamoDB | Eventual (with Strongly Consistent Reads enabled) | CAP: CP (Consistency + Partition tolerance) | Guarantees read consistency only if you enable it; otherwise, eventual consistency. |
| RDS (Aurora) | Strong (for MySQL-compatible) | CAP: CP | Uses multi‑AZ replication for durability. |
| SNS | Eventual (replicated across regions) | CAP: AP | Focused on availability, not immediate consistency across subscribers. |
Understanding CAP helps architects decide when to sacrifice consistency for availability in a global, fault‑tolerant system.
3. AWS Global Infrastructure
3.1. Regions, Availability Zones, Edge Locations
| Component | Definition | AWS Example | Edge Cases |