Begin with a familiar project
Let us take a college website. It needs an application, uploaded files and a way for visitors to reach it. I would write these needs on paper first. Only then would I connect them to compute, storage and networking services.
Learn the role of each service
EC2 gives you virtual servers, S3 provides object storage and VPC gives you a virtual network. Each solves a different part of the problem. You do not need to memorise the complete service catalogue before starting a small project.
Keep cost and responsibility together
For every service you learn, ask who gets access, how charges are calculated and how you will recover data. Finish the exercise by reviewing resources and cleanup. This habit is more useful than remembering a list of service names.
Try it yourself
Draw a three-box website diagram for application, files and network. Write one requirement inside each box before selecting a service.
A common question
Do I need to learn every AWS service?
No. Start with the services required for one small application, then expand as new requirements appear.
References & video notes
Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.
Keep learning
- Public, private and hybrid cloud explained
- IaaS vs PaaS vs SaaS: who manages what?
- AWS Regions and Availability Zones explained