Open In App

Amazon VPC – Introduction to Amazon Virtual Private Cloud

Amazon VPC or Amazon Virtual Private Cloud is a service that allows its users to launch their virtual machines in a protected as well as isolated virtual environment defined by them. You have complete control over your VPC, from creation to customization and even deletion. It’s applicable to organizations where the data is scattered and needs to be managed well. In other words, VPC enables us to select the virtual address of our private cloud and we can also define all the sub-constituents of the VPC like subnet, subnet mask, availability zone, etc on our own. 

What is Amazon VPC(Virtual Private Cloud)?

Amazon VPC can be referred to as the private cloud inside the cloud. It is a logical grouping of servers in a specified network. The servers that you are going to deploy in the Virtual Private Cloud(VPC) will be completely isolated from the other servers that are deployed in the Amazon Web Services. You can have complete control of the IP address to the virtual machines and route tables and gateways to the VPC. With the help of security groups and network access control lists, you can protect your application more.



Amazon VPC (Virtual Private Cloud) Architecture

The basic architecture of a properly functioning VPC consists of many distinct services such as Gateway, Load Balancer, Subnets, etc. Altogether, these resources are clubbed under a VPC to create an isolated virtual environment. Along with these services, there are also security checks on multiple levels. 

It is initially divided into subnets, connected with each other via route tables along with a load balancer. 



Amazon VPC (Virtual Private Cloud) Components

VPC

You can launch AWS resources into a defined virtual network using Amazon Virtual Private Cloud (Amazon VPC). With the advantages of utilizing the scalable infrastructure of AWS, this virtual network closely mimics a conventional network that you would operate in your own data center. /16 user-defined address space maximum (65,536 addresses)

Subnetes

To reduce traffic, the subnet will divide the big network into smaller, connected networks. Up to /16, 200 user-defined subnets.

Route Tables

Route Tables are mainly used to Define the protocol for traffic routing between the subnets.

Network Access Control Lists

Network Access Control Lists (NACL) for VPC serve as a firewall by managing both inbound and outbound rules. There will be a default NACL for each VPC that cannot be deleted.

Internet Gateway(IGW)

he Internet Gateway (IGW) will make it possible to link the resources in the VPC to the Internet.

Network Address Translation (NAT)

 Network Address Translation (NAT) will enable the connection between the private subnet and the internet.

Amazon VPC (Virtual Private Cloud) Fundamentals

Subnet

Internet Gateway

Route Table

NACL Network Access Control Lists

 Classless Inter-Domain Routing (CIDR)

RFC1918 Address(Private address)

The following networks are included in the RFC1918 address(Private address) 

10.0.0.0 -10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

 Amazon VPC Network Address Translation (NAT) 

Use cases of Amazon VPC

Amazon VPC (Virtual Private Cloud) Working

Follow the Setps Mentioned Below To Configure Virtual Private Cloud(VPC)

Setp 1: Login into AWS Console and navigate to the VPC as shown below.

Step 2: After navigating to the AWS VPC know click on create VPC.

Step 3: Configure all the details required to create as shown in the image below. Some of the most required settings to configure VPC was as follows

Step 4: Virtual Private Cloud Created successfully with the required setting to us.

Step 6: Check the VPC dashboard weather the VPC created is avalibile to use as shown in the image below GFG-VPC.

What Is AWS VPC (Virtual Private Cloud) Peering?

Amazon Virtual Private Cloud (VPC) is an private cloud where you can deploy your AWS Virtual machines with controlled access it is completely isolated from the each other the servers which are in the one VPC cannot communicate with the other virtual machines in the another virtual private network.

VPC peering can establish the connection between two Virtual Private Clouds which enables you to route the traffic between two VPCs using the IP address. The virtual servers which are in the same network can communicate with each other with out VPC peering connections but the servers which are in the two different networks can’t communicate with each other with out VPC peering.

AWS VPC (Virtual Private Cloud) Console 

We can create and manage VPCs using the AWS Management Console log in to your AWS account. Once you are redirected to the AWS management console. Click on “Services”, and a list of options will be visible. Under “Networking & Content Delivery” there is an option named VPC, and there is the navigation pane, which consists of various services as options. Refer to the image attached ahead for a better understanding. We have discussed some of the important resources. 

AWS Command Line Interface (AWS CLI)

We may issue commands on our own (OS) by using Windows, Mac, and Linux computers using AWS command line tools (OS). By using the command line, we can make it more expedient and quick than the console.

FAQs On Amazon VPC(Virtual Private Cloud)

1. Amazon VPC Full Form

The full form of Amazon VPC is Virtual Private Cloud which is isolated cloud with in the Amazon Web Service Cloud.

2. Amazon VPC Traffic Mirroring

Amazon VPC traffic mirroring is an feature provided by the amazon by which you can replicate the traffic from source instance to the target instance for the analysis or troubleshooting.

3. Amazon VPC Lattice

Amazon VPC is fully managed application networking service which streamlines the process of connecting,securing and monitoring application across the multiple AWS accounts and VPC’s which will reduce the efforts developers and can focus on the developing part.

4. Amazon VPC Flow Logs

Amazon VPC flow logs will helps you to monitor carefully the in and out of the traffic through the network the logs will stored in the CloudWatch, Amazon S3 or Amazon Kinesis data firehose.


Article Tags :