VPC Architecture
VPC Architecture
When a VPC is first created, then Route Table is automatically created, Network ACLs (Network Access Control List) and a default Security
Groups are also created by Default.
After that Internet gateway is created so that the VPC can be connected to the internet for outside world.
A subnet is a subsection of a network. Public subnets have a route table that points to an Internet Gateway. Private subnets have a
route table not pointed to an Internet Gateway. Subnets separate a network into subsections. Subnets currently do not have the
ability to span across Availability Zones, they can only exist in the AZ where they were created.
A security group is not a firewall on the subnet level. A security group is a firewall on the instance level.
NAT gateways:- a network address translation (NAT) instance in a public subnet in your VPC to enable instances in the private subnet
to initiate outbound IPv4 traffic to the internet or other AWS services, but prevent the instances from receiving inbound traffic initiated
by someone on the internet. Network ACLs:- A network access control list (ACL) is an optional layer of security for your VPC that
acts as a firewall for controlling traffic in and out of one or more subnets. Acts like a bouncer.
AWS Transit Gateway -- Easily connect Amazon VPCs, AWS accounts, and on-premises networks to a single gateway thru a
central hub.
AWS Private Link -- Establish private connectivity between VPCs and services hosted on AWS or on-premises, without exposing data
to the internet.
AWS Network Firewall -- Deploy network security across your Amazon VPCs with just a few clicks.
AWS VPN -- Extend your on-premises networks to the cloud and securely access them from anywhere.
Network address translation (NAT) gateway -- Allow your VPC private subnet workloads to access the internet while preventing the
internet from initiating a connection with those instances