Aws VPC
Aws VPC
Aws VPC
Amazon Virtual Private Cloud (Amazon VPC) enables us to launch AWS resources
into a virtual network that we've defined.
Best Practice to always create our own VPC with our own Settings and
Configuration.
Route table: A set of rules, called routes, that are used to determine
where network traffic is directed.
Launch instances in a subnet of our choice. we can choose our own subnet
addressing.
Public IP is must to setup the inter VPC communication But Two VPCs can be
linked via PVC Peering.
VPC Peering:
we can peer VPC's with other AWS accounts as well as other VPCs in the same
account.
we can peer between regions. Suppose we have one VPC in one region and other
VPC in another region, then we can peer the VPCs between different regions.One
VPC can be connected via 1 or more VPCs.
Subnet in VPC:
Virtual private cloud (VPC) is a virtual network dedicated to our AWS account.
It is logically isolated from other virtual networks in the AWS Cloud.
When we create a VPC, we must specify a range of IPv4 addresses for the VPC
in the form of a Classless InterDomain Routing (CIDR) block 10.0.0.0/16 is the
primary CIDR block for your VPC.
VPC spans all of the Availability Zones in the Region. After creating a
VPC, we can add one or more subnets in each Availability Zone.
VPC and subnet sizing for IPv4: 10.0.0.0 - 10.255.255.255 (10/8 prefix) -
User VPC must be /16 or smaller,
The allowed block size is between a /28 netmask and /16 netmask.
CIDR block must not overlap with any existing CIDR block that's associated
with the VPC. User cannot increase or decrease the size of an existing CIDR
block.
User can specify separate rules for inbound and outbound traffic.
There are quotas on the number of security groups that we can create per VPC,
the number of rules that we can add to each security group, and the number of
security groups that we can associate with a network interface.