Improve AWS load balancer health monitoring
Define a no-auth helper application for use with AWS load balancing health monitoring.
Before you begin
Ensure that you have access to:
- The AWS EC2 console, used to determine the internal IP address of Access Gateway high availability instances.
- The Access Gateway admin console running in AWS.
- Determine internal AWS IP addresses:
- Open a browser to the AWS EC2 console at https://console.aws.amazon.com/ec2/
- Sign in to the AWS Console.
- Scroll to and expand Instances.
- Click Instances.
- Examine the list of instances. Note the Private IP Address of each cluster member.
If the private IP address is inactive, click Settings and selectPrivate IP Address to activate it.
Create no-auth applications:
- Return to or open a browser to the Access Gateway Admin UI console.
- Select the Applications tab.
- For each IP address, create an associated application:
- Click Add.
- Select No-auth.
- In the Essentials tab, specify:
Field Value Name An appropriate name for the application, such as LBHealth-Admin, where the suffix distinguishes the application from other health monitoring applications. Public Domain Enter the associated public IP address.
Protected Web Resource
Leave unchanged as initially populated by wizard.
- Click Next. The Attributes tab opens.
- Click Next. The Policies tab opens.
- Click Done.
For each high availability node, create a no-auth application associated with the private IP address. These applications return a value of 200 on success. 200 is the default HTTP return code for a healthy instance.
Configure Load Balancer to use HTTP 200 return code:
- Return to the AWS Console.
- In the navigation pane, under Load Balancing, click Load Balancers. This displays a list of all defined load balancers.
- Select the load balancer that you created.
- Select the Health Check tab.
- Click Edit Health Check.
- Change the return code to 200.
- Click Save.