Exploring Application Load Balancer Target Groups
- Hafeez Baig |
- 23 steps |
- 2 minutes
Refer to the following guide to learn how to use IAM in the cloud\
<https://scribehow.com/shared/Creating_an_IAM_User_and_User_Group_in_AWS_Management_Console__hWNiiXlcRJKFqYZZEJD-cg>
Refer to this guide to learn how to create an Application Load Balancer<https://scribehow.com/shared/AWS_Elastic_Load_Balancing__Getting_started_with_ALB__EwQ9heoPR7SOessSgfviWA>
1
Sign in to **AWS Management Console** as an **IAM User**
**Pre-requisite** - Ensure you have selected the AWS region closest to your location\
For this guide, we will be using us-east-2 (Ohio) as a preferred choice
2
Type **EC2** in the search bar and click on **EC2** to view the EC2 Dashboard
3
On the EC2 dashboard click on **Target Groups** from the left bar to view the Target groups
4
Select and checkbox the "**my-target-group**" Target group to view its details
5
Scroll to the overview section to view all the details of the selected Target group
6
Click on the **Attributes** tab to view all the Attributes
7
On the right side of the attributes section, click on **Edit** button
8
Edit target group attributes wizard will open, set the **Deregistration delay** to **300** seconds
**What is the Deregistration delay in AWS?**
In AWS, the "Deregistration Delay" refers to the time that an Elastic Load Balancer (ELB) waits before deregistering an instance after it stops receiving traffic. This delay is intended to prevent the premature removal of an instance from the load balancer's pool in case it becomes temporarily unavailable or unresponsive due to network fluctuations or other issues.
9
Scroll to the **Slow start duration** and set it to **0** seconds
**What is Slow Start Duration in AWS?**
In AWS, "Slow Start Duration" is a feature available in Elastic Load Balancers (ELB) and Application Load Balancers (ALB). It refers to the time during which the load balancer gradually increases the traffic routed to a newly registered target.
10
Scroll to the **Target selection configuration** and set the Cross-zone load balancing to **Inherit settings from load balancer attributes**
Setting the Cross-zone load balancing to **Inherit settings from load balancer attributes** ensures that the load balancer's configuration for cross-zone load balancing is applied to the target group. This helps maintain consistency and simplifies management, as any changes made to the load balancer's cross-zone load balancing settings will automatically be inherited by the target group.
11
Click the **Save changes** button to apply the updates
12
Click on the **Targets** tab to register the Targets
13
On the right side, click on **Register targets** button
**Why do we need to register targets in AWS?**
In AWS, registering targets is necessary for load balancers to distribute incoming traffic effectively across multiple instances or resources. This process allows the load balancer to monitor the health of each registered target and route traffic only to healthy instances.
14
You can opt for instances from the pool of available Instances options to focus on.
15
Click on the **Health checks** tab to edit the Health checks
