In the AWS Region for the Outpost, they are not used. You can register targets by instance ID or IP address. Reports an event to the AWS Health Dashboard and the If you do not have sufficient instanceĬapacity or available IP addresses to scale the load balancer, the load balancer You need additional capacity, the load balancer adds 4xlarge After scaling the nodes to the largest instance size, if The load balancer scales as needed, resizing the nodes one size at a timeĤxlarge). The supported instance types are shown in the following The load balancer requires two large instances on the Outpost for For more information, see the AWS Outposts User Guide. You must have a reliable network connection between your Outpost and itsĪWS Region. You must have installed and configured an Outpost in your on-premises dataĬenter. Timeouts when attempting to establish a connection. To serve traffic, but the stalled scaling attempt may cause 5xx errors or To scale, the Application Load Balancer will run with insufficient capacity. Note: If an Application Load Balancers subnet runs out of usable IP addresses while attempting

Without them your Application Load Balancer could experienceĭifficulties with node replacement attempts, causing it to enter a failed state. Your load balancer uses these IP addresses toĮstablish connections with the targets.

These eight IP addresses are required to allow the loadīalancer to scale out if needed. Least eight free IP addresses per subnet. To ensure that your load balancer can scale properly, verify that eachĪvailability Zone subnet for your load balancer has a CIDR block with at least a The following restrictionsĮach subnet must be from a different Availability Zone. You must select at least two Availability Zone subnets.

Waf load balancer