

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 5
click for more info
Not enough gems
Cost: 6 gems
1: EC2 Instance Configuration: Keys
incomplete
2: EC2 Instances
incomplete
3: AMIs and Instance Types
incomplete
4: Public IPs
incomplete
5: Elastic IPs
incomplete
6: Security Groups
incomplete
7: SSH to Our Server
incomplete
8: Deploy the PatientPing Site
incomplete
9: Open Web Traffic
incomplete
10: Creating and Using Your Own AMI
incomplete
11: Reserved Instances and Savings Plans
incomplete
12: Auto Scaling Groups
incomplete
13: Launch Template
incomplete
14: Launch from Template
incomplete
15: Spot Instances
incomplete
16: Stateful and Stateless Applications
incomplete
17: Optional Cleanup
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Let's talk a bit more about the choices we made when launching that EC2 instance.
We chose the "Amazon Linux" AMI (Amazon Machine Image) to boot our virtual machine. This contains the baseline software for the server. Most AMIs just include an operating system like Ubuntu Linux or Windows Server 20XX, while others include full software stacks from a vendor.
You can also make your own AMIs, which is helpful if you're going to be repeating the same configuration over and over again (we'll talk about autoscaling later) or moving a server to a different region. It's a full VM image, not just a container (like Docker)!
We then chose an instance type to use. This just defines what hardware resources are attached to our server. Think CPU, memory, GPU, the type of processor/networking card, etc.
Ours is a fairly small machine, t3.micro (~$7.60/month). There are also huge gold-plated servers with lasers like u7in-32tb.224xlarge (~$263,520/month). (Okay, it doesn't actually have gold plates or lasers... but for that price maybe it should.)