If enabled, NLB supports active-standby backends. The standby backend takes over the traffic when the active node fails, and continues to serve the traffic even when the old active node is back healthy.
An array of backends.
IP version associated with the backend set.
If enabled, the network load balancer will continue to distribute traffic in the configured distribution in the event all backends are unhealthy. The value is false by default.
If enabled existing connections will be forwarded to an alternative healthy backend as soon as current backend becomes unhealthy.
If enabled along with instant failover, the network load balancer will send TCP RST to the clients for the existing connections instead of failing over to a healthy backend. This only applies when using the instant failover. By default, TCP RST is enabled.
If this parameter is enabled, the network load balancer preserves the source IP of the packet forwarded to the backend servers. Backend servers see the original source IP. If the {@code isPreserveSourceDestination} parameter is enabled for the network load balancer resource, this parameter cannot be disabled. The value is true by default.
A user-friendly name for the backend set that must be unique and cannot be changed.
Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot contain spaces. Avoid entering confidential information.
Example: {@code example_backend_set}
The network load balancer policy for the backend set.
Example: {@code FIVE_TUPLE}
The configuration of a network load balancer backend set. For more information about backend set configuration, see Backend Sets for Network Load Balancers.
*Caution:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.