Default VPC overview in AWS - Step-by-Step Execution

Process Flow - Default VPC overview

AWS Account Created

↓

Default VPC Automatically Created

↓

Default VPC Contains

↓

One Default Subnet

↓

Resources Can Use Default VPC

↓

Launch Instances

When you create an AWS account, a default VPC is created automatically with default subnets, an internet gateway, and a route table so you can launch resources easily.

Execution Sample

AWS

aws ec2 describe-vpcs --filters Name=isDefault,Values=true
aws ec2 describe-subnets --filters Name=vpc-id,Values=<default-vpc-id>
aws ec2 describe-internet-gateways --filters Name=attachment.vpc-id,Values=<default-vpc-id>

These commands show the default VPC, its subnets, and its internet gateway in your AWS account.

Process Table

Step	Action	Resource Created/Found	Details
1	AWS account created	Default VPC	VPC with default CIDR 172.31.0.0/16 created automatically
2	Default subnet created	Subnet	One subnet per Availability Zone with CIDR 172.31.x.0/20
3	Internet Gateway attached	Internet Gateway	Allows internet access for resources in default VPC
4	Route Table created	Route Table	Route to Internet Gateway for 0.0.0.0/0 traffic
5	Resources launched	EC2 Instances	Can launch instances using default VPC and subnets
6	Check default VPC	Describe VPCs	Filters show default VPC exists
7	Check subnets	Describe Subnets	Lists subnets associated with default VPC
8	Check internet gateway	Describe Internet Gateways	Shows internet gateway attached to default VPC
9	End	N/A	All default VPC components verified

💡 All default VPC components are created and ready for use after AWS account creation

Status Tracker

Resource	Initial State	After AWS Account Creation	After Default VPC Setup	Final State
VPC	None	Default VPC created	Default VPC exists with CIDR 172.31.0.0/16	Default VPC ready
Subnet	None	None	One subnet per AZ created	Subnets ready in default VPC
Internet Gateway	None	None	Internet Gateway created and attached	Internet Gateway attached
Route Table	None	None	Route Table created with route to IGW	Route Table ready

Key Moments - 3 Insights

Why do I see a VPC already created when I first log into AWS?

AWS automatically creates a default VPC for you when your account is created, as shown in execution_table step 1.

Can I launch EC2 instances without creating a VPC?

No, because the default VPC exists and is ready to use, you can launch instances immediately without creating a new VPC (see step 5).

What allows my instances in the default VPC to access the internet?

The internet gateway attached to the default VPC (step 3) and the route table directing traffic to it (step 4) enable internet access.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the internet gateway attached to the default VPC?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Resource Created/Found' column for 'Internet Gateway' in the execution_table.

According to variable_tracker, what is the state of subnets after AWS account creation but before default VPC setup?

A None

B One subnet per AZ created

C Subnets ready in default VPC

D Internet Gateway attached

💡 Hint

Look at the 'Subnet' row and the 'After AWS Account Creation' column in variable_tracker.

If the internet gateway was not attached, which step in execution_table would be missing?

A Step 1

B Step 6

C Step 3

D Step 8

💡 Hint

Step 3 shows the internet gateway attachment in execution_table.

Concept Snapshot

Default VPC is created automatically when you create an AWS account.
It includes one subnet per availability zone, an internet gateway, and a route table.
This setup lets you launch instances immediately with internet access.
You can view default VPC components using AWS CLI commands.
No extra setup is needed to start using the default VPC.

Full Transcript

When you create an AWS account, AWS automatically creates a default virtual private cloud (VPC) for you. This default VPC has a network range (CIDR block) of 172.31.0.0/16. It also creates one subnet in each availability zone with a smaller network range. An internet gateway is attached to the default VPC to allow internet access. A route table is created with a route that sends all internet traffic to the internet gateway. This setup means you can launch EC2 instances right away without creating your own VPC or networking components. You can check these resources using AWS CLI commands that filter for the default VPC and its components. This automatic setup helps beginners start using AWS networking easily.

Practice

1. What is the main purpose of the AWS Default VPC?

easy

A. To monitor application performance

B. To store data backups automatically

C. To provide a ready-to-use network for launching resources quickly

D. To manage user permissions and roles

Solution

1. Step 1: Understand what a VPC is

   A VPC is a virtual network where AWS resources run.

2. Step 2: Identify the role of the Default VPC

   The Default VPC is pre-made to let users launch resources without extra setup.

3. Final Answer:

   To provide a ready-to-use network for launching resources quickly -> Option C

4. Quick Check:

   Default VPC = ready network [OK]

Hint: Default VPC means ready network for quick resource launch [OK]

Common Mistakes:

• Confusing VPC with storage or permissions
• Thinking Default VPC manages backups
• Assuming Default VPC monitors performance

2. Which of the following is TRUE about the Default VPC's subnets?

easy

A. Subnets must be created manually before use

B. It has no subnets by default

C. It only has private subnets without internet access

D. It includes one subnet in each Availability Zone

Solution

1. Step 1: Recall Default VPC subnet setup

   The Default VPC automatically creates one subnet per Availability Zone.

2. Step 2: Check internet access for subnets

   These subnets are public and have internet access by default.

3. Final Answer:

   It includes one subnet in each Availability Zone -> Option D

4. Quick Check:

   Default VPC = subnet per AZ [OK]

Hint: Default VPC auto-creates subnets per AZ [OK]

Common Mistakes:

• Thinking Default VPC has no subnets
• Assuming subnets are private only
• Believing subnets require manual creation

3. If you launch an EC2 instance in the Default VPC, what is the default behavior regarding internet access?

medium

A. The instance automatically gets a public IP and internet access

B. The instance can only access other instances in the same subnet

C. The instance has no internet access unless manually configured

D. The instance is blocked from all network traffic by default

Solution

1. Step 1: Understand Default VPC internet setup

   Default VPC subnets are public and assign public IPs automatically.

2. Step 2: Check instance network behavior

   Instances launched get internet access by default through the internet gateway.

3. Final Answer:

   The instance automatically gets a public IP and internet access -> Option A

4. Quick Check:

   Default VPC instance = public IP + internet [OK]

Hint: Default VPC instances get public IPs automatically [OK]

Common Mistakes:

• Assuming no internet without manual setup
• Thinking instances are isolated by default
• Believing network traffic is blocked initially

4. You try to launch an EC2 instance in the Default VPC but get a network error. What is the most likely cause?

medium

A. The Default VPC was deleted or modified incorrectly

B. You forgot to create a subnet manually

C. The instance type is not supported in the Default VPC

D. AWS does not allow EC2 in Default VPC

Solution

1. Step 1: Recall Default VPC properties

   Default VPC exists by default with subnets and internet gateway.

2. Step 2: Analyze network error cause

   If network errors occur, it often means the Default VPC was deleted or changed wrongly.

3. Final Answer:

   The Default VPC was deleted or modified incorrectly -> Option A

4. Quick Check:

   Network error = Default VPC missing/changed [OK]

Hint: Network errors often mean Default VPC missing or changed [OK]

Common Mistakes:

• Assuming subnets must be created manually
• Thinking instance type blocks launch
• Believing EC2 is disallowed in Default VPC

5. You want to launch a private EC2 instance without internet access using the Default VPC. What should you do?

hard

A. Launch in the Default VPC subnet and disable the public IP

B. Create a new private subnet in the Default VPC and launch the instance there

C. Use the Default VPC as is; all instances are private by default

D. Delete the Default VPC and create a custom VPC with no internet gateway

Solution

1. Step 1: Understand Default VPC subnet types

   Default VPC subnets are public with internet access by default.

2. Step 2: Plan for private instance launch

   To have a private instance, create a new private subnet without internet gateway attachment.

3. Step 3: Avoid deleting Default VPC unnecessarily

   Deleting Default VPC is not required; just add private subnet inside it.

4. Final Answer:

   Create a new private subnet in the Default VPC and launch the instance there -> Option B

5. Quick Check:

   Private instance = new private subnet in Default VPC [OK]

Hint: Add private subnet in Default VPC for no internet [OK]

Common Mistakes:

• Assuming disabling public IP alone makes instance private
• Thinking all Default VPC instances are private
• Deleting Default VPC unnecessarily