

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
In the IPv4 address space, some address blocks are open for the public internet, while others are reserved for private use (for example, within a corporate or home network).
The rules surrounding these address blocks are defined in standards documents like RFC 1918 and RFC 6598.
The important idea for us is that servers in an AWS VPC usually communicate with one another using private IP addresses, and use public IP addresses only to communicate with systems outside the VPC (like the internet).
All of our servers on AWS have private IP addresses, and some will also have public addresses, but only if necessary. The CIDR that we set when we created our VPC, 10.0.0.0/22, falls within one of the private IP address ranges.
Any IPv4 address that starts with 10. is private.
Public IPs cost money, so we'll use them sparingly!