

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
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
Our PatientPing server does need a public IP address to be reachable on the internet, but we're going to use an "Elastic IP address" (EIP). This is an address that we can attach to any of our servers and move around as needed. You might be thinking:
"But Zach, why not just use the nice automatic public IP address?"
Well, the "auto-provisioned IP address" that we opted not to use earlier has a few downsides:
Most residential Internet Service Providers (ISPs) don't make any guarantees about the public IP address that you get assigned. ISPs often change and rotate IP addresses at their convenience. Which gives folks trying to run a little server out of their house wonderful hoops to jump through.
Allocate and associate an Elastic IP to patientping-web.
Cost check: Elastic IPs used to be free, but that's changed. All public IP addresses now cost $0.005/hour, or about $3.60/month.
Run and submit the CLI tests.
If you want to use the CLI instead, here's the command structure:
# Allocate an Elastic IP
aws ec2 allocate-address --domain vpc
# Associate it with an instance
aws ec2 associate-address --instance-id INSTANCE-ID --allocation-id ALLOCATION-ID