Attaches a backend server to a dedicated-bandwidth Global Acceleration instance.

Note the following before you call this action:

  • Only a VPC ECS instance or a VPC SLB instance can be attached to a dedicated-bandwidth instance.
  • A dedicated-bandwidth instance can be associated with only one backend server.

  • A backend server can be attached to multiple dedicated-bandwidth instances.

  • The backend server and the dedicated-bandwidth instance must belong to the same account.

  • The backend server to attach must be in the service area of the dedicated-bandwidth instance.
  • Only dedicated-bandwidth instances support attaching a backend server by using this API.

Debug

By using API Explorer, you can easily debug APIs, automatically generate SDK code examples, and quickly search for APIs.

Request parameters

Parameter Type Required? Example value Description 
Action String Yes AssociateGlobalAccelerationInstance

The name of this action.  Value: 

AssociateGlobalAccelerationInstance

BackendServerId String Yes i-saf23xxxxxxx

The ID of the backend server.

BackendServerRegionId String Yes cn-shanghai

The region where the backend server is located. It must belong to the service area of the dedicated-bandwidth instance.

GlobalAccelerationInstanceId String Yes ga-lsajj32xxxxxxx

The ID of the dedicated-bandwidth instance.

RegionId String Yes cn-hangzhou

The ID of the region where the dedicated-bandwidth instance is located.

To query the region ID, call DescribeRegions.

BackendServerType String No EcsInstance

The type of the backend server. Valid values:

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

Response parameters

Parameter Type Example value Description
RequestId String DDF2CC38-76C7-4000-909D-B2088158AEDA The ID of the request.

Examples

Request example


https://vpc.aliyuncs.com/?Action=AssociateGlobalAccelerationInstance
&BackendServerId=i-saf23xxxxxxx
&BackendServerRegionId=cn-shanghai
&GlobalAccelerationInstanceId=ga-lsajj32xxxxxxx
&RegionId=cn-hangzhou
&<CommonParameters>
Response example

XML format

<AssociateGlobalAccelerationInstanceResponse>
  <RequestId>DDF2CC38-76C7-4000-909D-B2088158AEDA</RequestId>
</AssociateGlobalAccelerationInstanceResponse>

JSON format

{
	"RequestId":"DDF2CC38-76C7-4000-909D-B2088158AEDA"
}

Error codes

HTTP status code Error code Error message Description
404 InvalidGlobalAccelerationInstanceId.NotFound The specified GlobalAccelerationInstanceId is not found. The specified Global Acceleration instance does not exist.
404 InvalidBackendServerId.NotFound The specified BackendServerId is not found. The specified backend server does not exist.
400 IncorrectGlobalAccelerationInstanceIdStatus Current GlobalAccelerationInstance status does not support this operation. The specified Global Acceleration instance does not support this operation.
400 InvalidBackendServerId.NotInVPC The specified BackendServerId is not in VPC. The specified backend server does not use the VPC network type.
400 TaskConflict.AssociateGlobalAccelerationInstance Operate too frequent. The system cannot process this many requests. Please try again later.
400 InvalidBackendServerRegionId.EqualRegionId The specified BackendServerRegionId can not be the same as RegionId. The specified region ID and backend server region ID cannot be the same.
400 InvalidAssociation.Duplicated Specified instance already is associated. This instance is already attached to an EIP or Global Acceleration instance. To attach the instance to a different EIP or Global Acceleration instance, detach the current EIP or Global Acceleration instance first.
400 InvalidBackendServerType.NotFound The specified BackendServerType is not supported. The specified backend server type is not supported.
400 InvalidParameter The specified parameter is not valid. The specified parameter value is invalid.

See common error codes