A Overall "AWS" Part 5:- AWS VPC ( Networking Concepts )

In previous blogs we cover  almost AWS CloudWatch Monitoring Part with set up an alarm Facility. Now we know what is aws, How to monitor our Resources, Resources List, What is the purpose that Resources. Now we will move on to the Concept Of Networking in AWS Platform.

In AWS, A VPC(Virtual Private Cloud) plays a major role. 

* Virtual Private Cloud  helps to connect multiple system in same network.

* VPC isolation network within a region.

* Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the 

AWS Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. 

You can use both IPv4 and IPv6 in your VPC for secure and easy access to resources and applications.

You can easily customize the network configuration for your Amazon VPC. For example, you can create a public-facing subnet for your web servers that has access to the Internet, and place 

your backend systems such as databases or application servers in a private-facing subnet with no Internet access. You can leverage multiple layers of security, including security groups and 

network access control lists, to help control access to Amazon EC2 instances in each subnet. 

When you create a VPC, you must specify a range of IPv4 addresses for the VPC in the form of a classless Inter-Domain Routing (CIDR) block; for example, 10.0.0.0/16. This is the primary 

CIDR block for your VPC.

Link:- AWS VPC Official Blog

Subnet:-

It is a subpart of vpc we can create different subnet in different availability zones. When you create a VPC, you must specify an IPv4 CIDR block for the VPC. The allowed block size is between a /16 netmask (65,536 IP addresses) and /28 netmask (16 IP addresses). After

you have created your VPC, you can associate secondary CIDR blocks with the VPC:-

Routing:- Providing a path to reach upto Destination.

IGW(Internet Gateway):-  It is used to connect a subnet to Internet. It is fully managed by AWS.

Elastic Ip:-

In every connection we must a "ip" address. In this AWS Cloud Management Platform We used  elastic Ip which means a Public ip. An Elastic IP address is a static, public IPv4 address designed for dynamic cloud computing. You 

can associate an Elastic IP address with any instance or network interface for any VPC in your account. With an Elastic IP address, you can mask the failure of an instance by rapidly remapping the address to another instance in your VPC. Note that the advantage of associating 

the Elastic IP address with the network interface instead of directly with the instance is that you can move all the attributes of the network interface from one instance to another in a single 

step.

NAT(N/W address Translator):- 

It is used generally Convert a ip from Private to Public.

In the NAT Gateways and instance are to be involved. A NAT Gateway managed by AWS and Instance are managed by us.

Internet Gateway:-

An internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between instances in your VPC and the internet. It therefore imposes no availability risks or bandwidth constraints on your network traffic. 

An internet gateway serves two purposes: to provide a target in your VPC route tables for internet-routable traffic, and to perform network address translation (NAT) for instances that 

have been assigned public IPv4 addresses.

In this blog we cover the Nominal Introduction Of essential concepts to creating a simple networking Connection within a region. We cover this Individual part in deep with its Practical demo in upcoming Blogs. Keep in touch.

 Thanks for reviewing.

 I hope you like it.