iTranslated by AI
From Buying to Building: A Beginner's Guide to Understanding AWS Like LEGO Bricks
*This page includes promotions.
Introduction: AWS is a "Giant Toolbox"
"There are over 200 AWS services, I can't possibly memorize all of them..."
When I first started studying AWS, I was overwhelmed by the sheer number of services.
However, one day it hit me:
"I don't need to memorize all of this. It's just a list of parts for a Lego set!"
Today, I will explain the joy of infrastructure building by reframing the complex world of AWS as a game of building blocks.
1. On-Premises is a "Custom Home," AWS is "Lego"
Traditional infrastructure building (on-premises) is like building a house.
You buy land, lay a foundation, build pillars... once you build it, it's not easy to move, and disposing of it is a huge hassle.
AWS, however, is different.
You simply click to place your favorite colored blocks into an infinite field (Region) in virtual space.
If you don't like how it looks, you can destroy (delete) it and rebuild it with the tip of your finger.
2. Learn the "Three Main Blocks"
Even with 200 services, everything is basically a combination of these three blocks:
-
EC2 (Elastic Compute Cloud):
- Role: "Computing block." The PC itself or the server.
- Image: Think of it as the "motor" or "processor" in Lego. Nothing works without this.
-
RDS (Relational Database Service):
- Role: "Storage block." A database to protect important data.
- Image: A sturdy "safe" part. A place to store your treasures—your data.
-
VPC (Virtual Private Cloud):
- Role: "Base plate."
- Image: The base board used to assemble blocks. This is your personal territory.
3. Assembling Blocks to Create a "System"
How do you connect these blocks? That is where an engineer's skill shines, and it is the most fun part.
For example:
- Lay down the base (VPC).
- Place the computing block (EC2).
- Place the safe (RDS).
- Connect them with lines (networks).
With just these, the basic form of a web service is complete.
If you need more, you can just add another block (EC2), and if you don't need them anymore, you can just remove them.
This "Agility" is the greatest benefit of using AWS.
A diagram representing the basic form of a web service
Conclusion: Start by Stacking Small Blocks
You don't need to build a giant castle from the start.
Try placing one EC2 block first. Then try connecting an RDS.
As you play around with them, you'll realize you've become a fine "Cloud Architect" before you know it.
It's okay to fail. After all, digital blocks can be destroyed as many times as you like, and the cost of rebuilding is only a few cents.
[PR] Recommended Introductory Book on "How to Stack Blocks"
If you want to learn the basic patterns of which blocks to combine, this book was the easiest to understand:
"AWS Operation Guide Revised 2nd Edition: Essential AWS Basics and Operational Know-How [AWS Deep Dive Guide]"

↓Book ↓Kindle
Discussion