
Disclaimer: This course contains the use of artificial intelligence.
AWS has around 200 services, and most courses handle that in one of two unsatisfying ways: they teach five of them in enormous depth, or they name all of them so quickly that nothing sticks. This course does something different. It explains what problem each service was invented to solve — because once the problem is clear, the service becomes obvious, and obvious things are hard to forget.
What You'll Learn
Part 1 covers the 40 core services that everything else in AWS sits on: compute, containers, storage, networking, and the edge. You will meet:
Compute & Containers: EC2, Auto Scaling, Lambda, Fargate, ECS, EKS, ECR
Storage & Backup: S3, EBS, EFS, FSx, AWS Backup
Networking & Edge: VPC, Elastic Load Balancing, Route 53, CloudFront, Transit Gateway, PrivateLink, Direct Connect, Outposts, and more
Each one is introduced through a practical situation where somebody genuinely needed it.
Story-Driven Learning
Every lesson is a story rather than a feature list. You follow one company—an online bookshop—as it grows:
Their database ends up on the wrong kind of disk.
Their website is fast in Britain and slow in Australia.
Their backup script quietly stops running for four months because Auto Scaling replaced the instance it was living on, exactly as designed.
Each problem is real, each one has a service that answers it, and by the end, you will be able to explain why that service exists in a single sentence.
Master the "X vs. Y" Trade-Offs
This approach prepares you for the interview questions everybody struggles with: "When would you use X instead of Y?"
Knowing that EFS is a shared filesystem is easy. Explaining that you reach for it when a third-party application demands a POSIX path and you cannot change the code is what gets you hired. This course is built around exactly those trade-offs:
Storage: EBS vs. EFS vs. FSx
Load Balancing: ALB vs. NLB
Global Delivery: CloudFront vs. Global Accelerator
Networking: VPC Peering vs. Transit Gateway vs. PrivateLink
Resilience: Backup vs. Disaster Recovery
Honest, Practical Guidance
It is equally honest about what you do not need. Several services covered here are ones most engineers will never buy, and the lessons say so plainly—along with the exact constraint that would change that answer. A course that recommends everything recommends nothing; being able to say "this isn't for my situation, and here's why" is a stronger interview answer than reciting a configuration screen.