Before you start: Review IP addresses, subnets and DNS if they are new to you.
What to aim for
Distinguish cloud service models and shared responsibility.
Explain the roles of EC2, S3, VPC, Route 53 and Lambda.
Try it yourself: Sketch a VPC, subnet and EC2 instance, then explain the route and access controls needed for internet connectivity. A drawing needs no cloud account.
Suggested preparation, not an entry requirement. Every track stays free to open.
Learn with Network Kings videos, ordered chapters and practical explanations. Choose a subject to see what to study and which lessons to watch first.
A little time. A new idea.
Bite-sized tech lessons from the channel
CCNP & CCIE
286 views
Explore more
452 views
Networking
353 views
CCNP & CCIE
2.3K views
Networking
1K views
Networking
599 views
Linux & DevOps
620 views
Networking
363 views
Explore more
368 views
Networking
608 views
Explore more
489 views
AWS
315 views
Video · Networking
Your browser paused autoplay. Press Play inside the video to start.
What is AWS VPC, Subnet & Routing Table with Practical.
Networking · 15:34
LEARNING CHAPTER
Understand. Remember. Apply.
AWS VPC
Subnets
Route tables
Internet connectivity
Based on the video transcript
Build a VPC, split its subnets and connect the route tables
The lesson introduces VPCs, subnets, routing and gateways, then starts the AWS console walkthrough at about 5:38 in the Mumbai region. It creates a 10.0.0.0/24 VPC, divides it into two /25 subnets, creates separate route tables and associates each subnet with its intended table. The public-side table gains a default route through an attached internet gateway. The recording stops before launching an EC2 instance or testing its internet access; NAT gateways, VPN and Direct Connect are introduced, not configured. The closing section describes a separate training program.
Key takeaways
A VPC is the logical network boundary; subnets divide its address space into smaller networks.
The demonstrated 10.0.0.0/24 block is split into the non-overlapping 10.0.0.0/25 and 10.0.0.128/25 subnet blocks.
Check the subnet association on each route table. A subnet name such as public is only a label; the associated routes determine its direct internet path.
For the public-side path, the walkthrough attaches an internet gateway to the custom VPC and adds 0.0.0.0/0 pointing to that gateway.
A saved route is not proof of working instance connectivity. EC2 setup and end-to-end internet testing are left for a later lesson.
Put it into practice
On paper, draw the 10.0.0.0/24 VPC and its two /25 subnets. Associate each subnet with its own route table, then add the internet-gateway default route only to the public-side table. If that route is accidentally added to the other table, explain which subnet's routing has changed and what still needs checking before claiming that an instance can reach the internet.
Explore the diagram / topology
Illustrative concept diagram for study.
Map the walkthrough's two subnet associations and the public-side default route. Dotted links show subnet-to-route-table associations, not packet hops. The private-side table has no direct internet-gateway default route in this example. A route alone does not prove instance internet access; EC2 setup and connectivity testing are not shown in this recording.
8 lessons
