AWS Networking key concept

 
A Network is a way of communication between devices. AWS Networking allows creating a fast, reliable, and secure network. To understand AWS Networking better, it is important to get familiar with all the Amazon services that create a network.

• IP — Address used to map requests to machines, can be public or private.
• VPC — A slice of the AWS cloud infrastructure
• Subnet – A portion of a larger network, usually a subnetwork of a VPC.
• Netmask — A way of denoting a range of IP used to splice up a network into subnets.
• Route Table — A set of rules that are assigned to a subnet which define how subnets communicate.
• Internet Gateway — An AWS resource that gives a subnet access to the public internet.

Security group — Essentially a firewall that dictates which traffic (via protocols and ports) can access a resource.

Lets see a basic application example which needs internet access running on EC2. So basic networking for this will be to define a VPC -->create subnets(public :- destination will be 0.0.0.0 via route table & private:- destination will be some cidr block via route table)--> internet gate way-->adding ingress rule in security group of EC2 instance above will solve your basic networking issue to get access from internet.

Now Lets go little deeper in networking concept and learn some other services as below :

AWS Private Link

AWS Private Link provides private connectivity between various amazon services. The connectivity is done between Amazon VPC (Virtual Private Cloud), Amazon Web Services, and on-premises network without exposing traffic to the public internet.

AWS Direct Connect

AWS Direct Connect helps in establishing a dedicated network from your premises to AWS. It enables a private and secure connection between AWS and the data center. It is compatible with AWS services and supports a high bandwidth for a more consistent network and better speed. The starting speed is around 50 Mbps and supports scaling up to 100 Gbps.

VPC peering vs Transit gateway vs Private link:-

Now if we have requirement to talk between multiple VPCs and underlaying resources then we have 3 choices: VPC peering, Transit gateway and Private link. Confused which one to choose now :-

VPC Peering is an excellent choice when you need to connect a limited number of VPCs with minimal cost implications and management overhead.

AWS Private Link is the right option when you intend to selectively expose services to other VPCs, although it involves additional costs, extra networking components, and the associated management overhead and it provides unidirectional access from a consumer VPC to a single service in a provider VPC.

Transit Gateway can serve as an alternative to VPC Peering as you scale to a larger number of VPCs, simplifying network management at the expense of some additional costs. It’s also well-suited for connecting various network entities with anticipated scalability. Transit Gateway provides full bidirectional layer 3 connectivity between VPCs – allowing full access to/from all resources in the connected VPCs.

Hope you must have learned something today...happy networking!