edit-icon download-icon

AssociateGlobalAccelerationInstance

Last Updated: Apr 13, 2018

Description

Bind a Global Acceleration instance to a backend server.

Note the following before binding a Global Acceleration instance to a backend server:

  • Only an ECS instance of the VPC network or an SLB instance of the VPC network can act as the backend server of a Global Acceleration instance.

  • You can only bind a Global Acceleration instance to one backend server.

  • You can bind multiple Global Acceleration instances to one backend server.

  • The instance acting as the backend server and the Global Acceleration instance must belong to the same account.

Request parameters

Name Type Required Description
Action String Yes

The action to perform.

Valid value: AssociateGlobalAccelerationInstance

RegionId String Yes

The region of the Global Acceleration instance.

You can obtain the region ID by calling the DescribeRegions API.

GlobalAccelerationInstanceId String Yes The ID of the Global Acceleration instance.
BackendServerRegionId String Yes The region of the backend server, which must belong to the service area of the Global Acceleration instance.
BackendServerType String No

The type of the backend server.

Valid values:

  • EcsInstance(default): ECS instance
  • SlbInstance: SLB instance

BackendServerId String Yes The ID of the backend server.

Response parameters

Name Type Description
RequestId String The ID of the request.

Error codes

See VPC API Error Center.

Examples

Request example

  1. https://vpc.aliyuncs.com/?Action=AssociateGlobalAccelerationInstance
  2. &RegionId=ap-southeast-1
  3. &GlobalAccelerationInstanceId=ga-aabbccddaabb
  4. &BackendServerRegionId=ap-northeast-1
  5. &BackendServerId=i-6we1ge5qfxxxxxx
  6. &BackendServerType=EcsInstance
  7. &<CommonParameters>

Response example

JSON format

  1. {
  2. "RequestId": "DDF2CC38-76C7-4000-909D-B2088158AEDA"
  3. }
Thank you! We've received your feedback.