3 Things They Don’t Tell You About Amazon EC2 Until You Break It 🖥️
Getting started with EC2? Here are three quick, hard-learned lessons every beginner needs to know before spinning up their first instance.
When beginners start learning AWS, Amazon EC2 (Elastic Compute Cloud) is almost always the very first service they try. The basic explanation is simple: "It's a virtual computer in the cloud."
While that is true, my early days of playing around with EC2 taught me a few quick lessons that tutorials often glaze over:
- Public IP Addresses are Fickle: If you stop an EC2 instance and start it back up, its public IP address will completely change! If you need a permanent IP address for a project, you must assign an Elastic IP (just remember to release it when you delete the server, or AWS will charge you for hoarding it).
- Security Groups are your Bouncers: If you launch a web server and the webpage refuses to load, 99% of the time your server is fine. You likely just forgot to open port 80 (HTTP) or 443 (HTTPS) in your attached Security Group. By default, they block everything coming in!
- Key Pairs are literally Keys: When you launch an instance, AWS gives you a
.pemfile to SSH into it. If you lose that file, you are essentially locked out of your own server. Treat it like the only physical key to your front door!
Starting with EC2 is a fantastic way to learn cloud infrastructure. What operating system do you usually choose for your EC2 test instances—Amazon Linux, Ubuntu, or Windows?
Let me know below, and leave a like if you’ve ever been burned by a missing Security Group rule!
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article