New Training: Plan for VPC Network Traffic
In this 7-video skill, CBT Nuggets trainer Bart Castle teaches you about network traffic flow and management in AWS Virtual Private Clouds (VPCs). Gain an understanding of IP routing in VPCs and common techniques for isolating, filtering, and controlling network traffic. Watch this new AWS training.
Learn AWS with one of these courses:
- AWS Certified Security – Specialty
- AWS Certified Cloud Practitioner
- AWS Certified Solutions Architect – Associate
- AWS Certified SysOps Administrator – Associate
- AWS Beginner Skills
- AWS Certified Developer – Associate
This training includes:
- 7 videos
- 37 minutes of training
You’ll learn these topics in this skill:
- Elastic Network Interface Concepts
- Working with Elastic Network Interfaces
- VPCs, SGs, and NACLs
- Public and Private Subnets
- Internet Access Checklist
- Internal VPC Traffic Flow
- VPC External Traffic Flows
Public vs Private Subnets for AWS VPC: What's the Difference?
Configuring resources in AWS Virtual Private Cloud can both be easy and feel daunting at the same time. AWS offers a lot of tools for configuring things like access control lists and private subnets. Though these tools have direct analogs in the traditional network environment, AWS admins still need to understand the differences between private and public subnets for their private cloud.
Public subnets have direct access to the internet. If a virtual private server is configured with an IP address on a public subnet, that VPS will have direct access to the public internet. Configuring instances with an IP on a public subnet should be done with great care. By default, using a public subnet should be avoided unless it's required for a resource to have direct, public-facing internet access (e.g. – A web server).
On the other hand, private subnets only have access to that virtual cloud space. That means a VPS configured with an IP on the private subnet will only be able to communicate with other resources within that private cloud. External access can be configured for a VPS on a private subnet with NAT, though.