Before I dive into writing about my weekly AWS projects and practicals, I wanted to start with the foundation that really shaped my understanding of cloud computing: Amazon EC2 (Elastic Compute Cloud).
Learning EC2 was the turning point for me. It helped me understand why certain services exist, how they connect, and when to use them.
(Not where I want to be yet — but trying to, step by step 💪)
🟢 Essential EC2 Services & Microservices I Learned
Here’s the list of core services and features I worked with that gave me clarity:
- EC2 Instance Types – General purpose, compute-optimized, memory-optimized, storage-optimized.
- Amazon Machine Images (AMIs) – Preconfigured OS + software stacks.
- Elastic Block Store (EBS) & Instance Store – Persistent vs ephemeral storage.
- Elastic Load Balancer (ELB) & Target Groups – Distributing traffic across instances.
- Auto Scaling – Scaling infrastructure dynamically.
- Security Groups & NACLs – Controlling inbound and outbound traffic.
- Elastic IPs & ENIs – Static IPs and virtual network cards.
- Placement Groups – Optimizing instance placement (cluster, spread, partition).
- Pricing Models – On-Demand, Reserved, and Spot Instances.
- EC2 User Data & Metadata – Automating configuration and fetching instance info.
- Systems Manager (SSM) Agent – Managing EC2 without SSH/RDP.
- CloudWatch Monitoring – Metrics, logs, and alarms. **
✨ Key Takeaway**
By learning and applying these, I started to see how AWS ties everything together into scalable, secure, and cost-effective systems.
🔜 What’s Next
Starting next week, I’ll be publishing weekly posts here on projects and real-world implementations I’ve built using these services.
If you’re just starting out, my advice (i am in no position but learnt something through this) : don’t rush past EC2. It’s the core of AWS and makes everything else much easier to understand.
🔗 Follow along if you’re also on this journey — let’s learn in public together! 🚀
Top comments (0)