AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
The instance must be a running instance in the same network as the load balancer (EC2-Classic or the same VPC). If you have EC2-Classic instances and a load balancer in a VPC with ClassicLink enabled, you can link the EC2-Classic instances to that VPC and then register the linked EC2-Classic instances with the load balancer in the VPC.
RegisterInstanceWithLoadBalancer completes when the request
has been registered. Instance registration takes a little time to complete. To check
the state of the registered instances, use DescribeLoadBalancers or DescribeInstanceHealth.
After the instance is registered, it starts receiving traffic and requests from the
load balancer. Any instance that is not in one of the Availability Zones registered
for the load balancer is moved to the
OutOfService state. If an Availability
Zone is added to the load balancer later, any instances registered with the load balancer
move to the
If you stop an instance registered with a load balancer and then start it, the IP addresses associated with the instance changes. Elastic Load Balancing cannot recognize the new IP address, which prevents it from routing traffic to the instances. We recommend that you use the following sequence: stop the instance, deregister the instance, start the instance, and then register the instance. To deregister instances from a load balancer, use DeregisterInstancesFromLoadBalancer.
For more information, see Deregister and Register EC2 Instances in the Elastic Load Balancing Developer Guide.
Version: (assembly version)
public abstract RegisterInstancesWithLoadBalancerResponse RegisterInstancesWithLoadBalancer( RegisterInstancesWithLoadBalancerRequest request )
Container for the necessary parameters to execute the RegisterInstancesWithLoadBalancer service method.
Supported in: 4.5, 4.0, 3.5