Aws VPC

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

Amazon Virtual Private Cloud (Amazon VPC)

Amazon Virtual Private Cloud (Amazon VPC) enables us to launch AWS resources
into a virtual network that we've defined.

Amazon VPC is the networking layer for Amazon EC2 Instances.

For Fresh account Amazon have default VPC Network.

Best Practice to always create our own VPC with our own Settings and
Configuration.

Few Key Points and Terminology:

Virtual private cloud (VPC): A virtual network dedicated to our AWS


account.

Subnet: A range of IP addresses in our VPC.

Route table: A set of rules, called routes, that are used to determine
where network traffic is directed.

Internet gateway: A gateway that we attach to our VPC to enable


communication between resources in our VPC and the internet.

VPC endpoint: Enables us to privately connect our VPC to supported AWS


services and VPC endpoint services powered by Private Link without requiring
an internet gateway, NAT device, VPN connection, or AWS Direct Connect
connection.

What user can do with VPC:

Launch instances in a subnet of our choice. we can choose our own subnet
addressing.

we can assign custom IP address ranges in each subnet.

we can configure route tables between subnets.

we can create an internet gateway and attach it to our VPC.

It provides much better security control over our AWS resources.

we can assign security groups to individual instances.

we also have subnet network access control lists (ACLS).

For Small or Medium Setup One VPC will be enough.


Amazon Virtual Private Cloud (Amazon VPC)

➤ An Instance Launched in one VPC can never communicate to Instance Launched


in another VPC via Private IP.

Public IP is must to setup the inter VPC communication But Two VPCs can be
linked via PVC Peering.

VPC Peering:

VPC Peering is a networking connection that allows us to connect one VPC


with another VPC through a direct network route using private IP addresses.
Instances behave as if they were on the same private network.

we can peer VPC's with other AWS accounts as well as other VPCs in the same
account.

Peering is in a star configuration, i.e., 1 VPC peers other 4 VPCs.

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.

➤ If a subnet's traffic is routed to an internet gateway, the subnet is known


as a public subnet.

If a subnet doesn't have a route to the internet gateway, the subnet is


known as a private subnet.

VPC and subnet sizing for IPv4: 10.0.0.0 - 10.255.255.255 (10/8 prefix) -
User VPC must be /16 or smaller,

for example, 10.0.0.0/16.


Amazon Virtual Private Cloud (Amazon VPC)

172.16.0.0 - 172.31.255.255 (172.16/12 prefix)-User VPC must be /16 or


smaller, for example, 172.31.0.0/16.

192.168.0.0 - 192.168.255.255 (192.168/16 prefix)-User VPC can be smaller,


for example 192.168.0.0/20.

To add a CIDR block to our VPC, the following rules apply:

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.

Security Group in AWS

Security group acts as a virtual firewall for your instance to control


inbound and outbound traffic.

Upto 5 SGs can be assigned to Instance in AWS.

SGs are Instance Level not Subnet Level.

Basics of Security Group in AWS

User can specify allow rules, but not deny rules.

User can specify separate rules for inbound and outbound traffic.

Security group rules enable us to filter traffic based on protocols and


port numbers.

By default, a Security Group don’t have any Inbound Rule.

By default, a security group includes an outbound rule that allows all


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.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy