Enable Access Gateway load balancing in an application
Load balancing enables you to distribute the request load for an application across multiple servers.
Configure load balancing
- In the Access Gateway Admin UI console, select the Applications tab.
- Click the pencil icon in the row containing the application to edit it.
- Select the Settings tab.
- Expand the Protected Web Resources tab.
- Select the Load Balancing option to enable it. A table appears that displays each hostname and its load-balancing weight.
- Click the pencil icon for a hostname to edit it.
- Select either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
- Optional. Enable the Host Header value option and specify a value for it.
- Click Add protected web resource.
- Enter a fully qualified hostname and port combination, such as https://backendserver1.atko.com:7001.
- Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled. Weights represent the percentage of requests to route to this host. If you configure one host with a weight of 2 and a second host with a weight of 1, the first host receives double the requests of the second host.
- Click Okay.
- Optional. Enable the Load Balancer Health Checks option. Health checks use GET operations to indicate that resources are functional. Resources that Okta classifies as unhealthy aren't routed new requests to them.
- Click Edit to modify the health check settings.
- Path: The URI to the resource verified by the health check. The default path is / (forward slash).
- Method: The HTTP method used by the health check. The default method is Always GET.
- Status code: The HTTP status code that indicates the health of the request. The default status code is 200.
- Interval: The interval between health check verifications in seconds. The default interval is 10 seconds.
- Request timeout: The timeout value in seconds. The default request timeout is one second.
- Healthy threshold: The number of successful requests that must be recorded before a host is considered healthy. The default healthy threshold is three requests.
- Unhealthy threshold: The number of failed requests that must be recorded for a host to be considered unhealthy. The default unhealthy threshold is three requests.
- Click Save.
- Click Done.