

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 4
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
With a VPC, subnets, and a key pair in hand, we're ready to launch our first AWS server instance.
Elastic Cloud Compute (EC2) is AWS' flagship service for running servers on their infrastructure. It's their answer to questions like:
Let's create an instance and look at the choices we have to make along the way.
Launch a t3.micro EC2 instance named patientping-web in patientping-public-a.
Cost check: The Linux server we provision here will cost $0.0104 per hour (in us-east-1). That means about $0.25 per day, or $7.60 per month. If you're on the free tier, it will be covered by that.
Remember to delete this server when you're done with it!
Go back to the "Instances" list and confirm the new patientping-web server is there.
Run and submit the CLI tests.
If you want to use the CLI instead, here's the command structure:
aws ec2 run-instances --image-id AMI-ID --instance-type TYPE --key-name KEY-NAME --subnet-id SUBNET-ID --security-group-ids SG-ID --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=INSTANCE-NAME}]'