Please enable JavaScript.
Coggle requires JavaScript to display documents.
VPC IN AWS (AMAZON WEB SERVICE) - Coggle Diagram
VPC IN AWS (AMAZON WEB SERVICE)
WHAT IS VPC (VIRTUAL PRIVATE CLOUD IN AWS)
A service that lets you launch AWS resources in a logically isolated virtual network that you define.
You have complete control over your virtual networking environment, including selection of your own IP addresses range, creation of subnets, and configuration of route tables and network gateways.
You can use IPv4 and IPv6 for most resources in your VPC, helping to ensure secure and easy access to resources and applications.
EXPLAIN PUBLIC AND ELASTIC IP ADDRESSES
Public IP Addresses
It is assigned to your launched instance.
when an instance is terminated the public IP attached to it gets released and further when you relaunch the same instance new IP address is assigned.
use case : Public IP is used when you are working on small projects and running 2-3 servers. Here in this situation you make use of IP for short time.
Elastic IP Addresses
It is assigned to your AWS account.
Elastic IP do not change and they remain same even if you terminate the instance and later again restart the same instance.
use case : Elastic IP is used when you are working on long time project and configuration of IP sometime consumes more time.
EXPLAIN ELASTIC NETWORK INTERFACES IN VPC
Primary and Secondary Private IP Addresses
Primary IP Addresses
Each instance receives a primary private IP object during launch.
The Networking service uses the Dynamic Host Configuration Protocol (DHCP) to pass the object's private IP address to the instance.
This address does not change during the instance's lifetime and cannot be removed from the instance.
The private IP object is terminated when the instance is terminated.
Secondary Private IP Addresses
You can add a secondary private IP to an instance after it's launched. You can add it to either the primary VNIC or a secondary VNIC on the instance.
The secondary private IP address must come from the CIDR of the VNIC's subnet.
ou can move a secondary private IP from a VNIC on one instance to a VNIC on another instance if both VNICs belong to the same subnet.
2 reason why we might use secondary private IPs :
Instance failover
: You assign a secondary private IP to an instance. Then if the instance has problems, you can easily reassign that secondary private IP to a standby instance in the same subnet. If the secondary private IP has a public IP assigned to it, that public IP moves along with the private IP.
Running multiple services or endpoints on a single instance
: For example, you could have multiple container pods running on a single instance, and each uses an IP address from the VCN's CIDR. The containers have direct connectivity to other instances and services in the VCN. Another example: you could run multiple SSL websites with each one using its own IP address.
Attaching Elastic Network Interface
You can attach a network interface to any of your stopped or running instances, using either the Instances or Network Interfaces pages of the Amazon EC2 console. Alternatively, you can specify an existing network interface or attach an additional network interface when you launch an instance.
DESCRIBE CIDR BLOCKS
Secondary CIDR Blocks
Similar to the primary CIDR block, secondary CIDR blocks are also supported by all the AWS services including Elastic Load Balancing and NAT Gateway.
This feature has two key benefits :
First, customers, who are launching more and more resources in their VPCs, can now scale up their VPCs on-demand.
Second, customers no longer have to over-allocate private IPv4 space to their VPCs - they can allocate only what is required at the time, and later expand it as needed.
IPv6 CIDR Blocks
IPv6 networks are written using CIDR notation and use the same CIDR technology as is employed by CIDR on IPv4.
Under CIDR, IPv6 unicast addresses can be aggregated with prefixes of arbitrary bit length, similar to IPv4 addresses.