AWS Builder Center

Builder Center

Day 6 Of Cloud with AWS: Subnets

#100DaysOfCloud challenge using AWS

In today's task:
Create one subnet named devops-subnet under default VPC.
Todo:
  • Create the resources only in us-east-1 region.
----------------------------------------------
Steps followed:
  1. Open VPC Service
  2. Find Default VPC
  3. Click on: Create Subnet
  4. Fill details: Select the default VPC
  5. Availability Zone: us-east-1a
  6. Fill IPv4 Subnet CIDR block
  7. Click Create Subnet button to create subnet.
----------------------------------------------
What is Subnet?
A Subnet (sub-network) is a smaller network created inside a larger network called a VPC (Virtual Private Cloud).
The VPC is the whole private cloud network.Subnets divide that network into smaller logical sections.
Why are subnets are required?
Without subnets:
  • everything sits in one flat network
  • security becomes difficult
  • traffic management becomes messy
  • scaling becomes hard
Subnets help with:
  • security
  • isolation
  • organization
  • routing
  • scalability
Types of Subnets
  1. Public Subnet
A subnet connected to the internet.
Usually contains:
  • Web servers
  • Load balancers
  • Bastion hosts
Example: Nginx, Apache, React frontend. These need internet access.
  1. Private Subnet
No direct internet access.
Usually contains:
  • Databases
  • Backend APIs
  • Internal services
Why?
Because databases should NOT be publicly reachable.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article