AWS NETWORK LOAD BALANCER-NLB

 

In AWS (Amazon Web Services), a Network Load Balancer (NLB) is a highly scalable load balancing solution that operates at the transport layer (Layer 4) of the OSI model. It is designed to handle high volumes of traffic and provide low-latency performance.

The Network Load Balancer is capable of distributing traffic across a group of targets, such as Amazon EC2 instances, containers, IP addresses, or AWS Lambda functions, in a single Availability Zone or across multiple Availability Zones. It uses flow-based load balancing, which allows it to handle millions of requests per second with extremely low latencies.

Here are some key features and benefits of the Network Load Balancer:

1. Highly scalable: The NLB is designed to handle high volumes of traffic and can scale to handle millions of requests per second. It automatically scales its capacity in response to incoming traffic patterns.
2. Low-latency performance: The NLB provides extremely low latencies by operating at the transport layer and forwarding traffic directly to targets without any proxying. It is ideal for latency-sensitive applications.
3. Support for TCP and UDP: The NLB supports both TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) traffic. It can load balance traffic for a wide range of applications and protocols.
4. Health checks and failover: The NLB performs health checks on targets to ensure they are available and healthy. It automatically distributes traffic only to healthy targets. If a target fails, the NLB detects it and routes traffic to healthy targets.
5. Cross-zone load balancing: The NLB evenly distributes traffic across multiple Availability Zones, which improves the availability and fault tolerance of your application.
6. Integration with other AWS services: The NLB integrates seamlessly with other AWS services like Auto Scaling, AWS Certificate Manager, and AWS CloudFormation, allowing you to build scalable and automated infrastructure.

When you configure a Network Load Balancer, you define one or more listeners to specify the incoming traffic’s port and protocol. You also create target groups to specify the targets that will receive the traffic. The NLB intelligently distributes traffic across the targets based on your load balancing configuration.

Create Two EC2 Instances:

Choose free tier server.t2.micro:

Create security-key:

Edit Network Settings:

Create Security Group:

Rules will be configured later in the lab:

Launch Instance 1:

Note: Also create the instance-2 in the default VPC but in a different zone.

Verification:

Configure IIS Server in both EC2 Instances:

First Connect EC2 Instances:

Create an index.html File In Both Instances:

CONFIGURE NLB:

Choose the Private IP Address for the EC2 Instances.

Configure default VPC.

Create Listener.

Create a Target Group.

Switch back to the load balancer and configure the target group in NLM.

NLB Verification.

Use the DNS Name of the Load Balancer to connect.

---

End Of Lab.