Service access endpoints¶
The Rackspace Cloud Load Balancers API service is a regionalized service. It allows the caller to select the region into which a load balancer is provisioned.
The following table lists the Rackspace Cloud Load Balancers endpoints that are available for each region.
To help you decide which regionalized endpoint to use, read about special considerations for choosing a region.
|Dallas/Ft. Worth (DFW)||
|Northern Virginia (IAD)||
|Hong Kong (HKG)||
Replace the sample account ID number,
1234, with your actual account number
that is returned as part of the authentication response. The account number is
located after the final slash (/) in the
The service catalog returned in the authentication response specifies the
correct service access endpoint for your account to use for accessing Cloud
Load Balancers. Use the service type (
rax:load-balancer) to locate the
correct endpoint in the service catalog. For an example of the service catalog,
see authentication response examples.
If you are load balancing cloud servers, you can determine the appropriate region to select by viewing your Cloud Servers list and creating a load balancer within the same region as the data center in which your servers reside. When your resources reside in the same region as your load balancer, devices are in close proximity to each other and can take advantage of ServiceNet connectivity for free data transfer between services.
ServiceNet is an internal Rackspace only, multitenant network connection within each Rackspace data center. ServiceNet IP addresses are not accessible via the public Internet. Rackspace customers can configure resources to use an internal IP address so that traffic over the ServiceNet network is not billed.
If you are load balancing external servers, you can determine the appropriate region to select by choosing the region that is geographically as close to your external servers as possible.