BandwidthPackageRemoveAccelerator - Global Accelerator - Alibaba Cloud Documentation Center

Disassociates a bandwidth plan from a Global Accelerator (GA) instance.

Operation description

BandwidthPackageRemoveAccelerator is an asynchronous operation. After you send a request, the system returns a request ID, but the operation is still being performed in the system background. You can call the DescribeBandwidthPackage operation to query the status of the bandwidth plan that you attempt to disassociate.
- If the bandwidth plan is in the unbinding state, it indicates that the bandwidth plan is being disassociated. In this case, you can perform only query operations.
- If the bandwidth plan is in the active state, it indicates that the bandwidth plan is disassociated.
The BandwidthPackageRemoveAccelerator cannot be called repeatedly for the same GA instance.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
ga:BandwidthPackageRemoveAccelerator	Write	BandwidthPackage acs:ga:{#regionId}:{#accountId}:bandwidthpackage/{#bandwidthPackageId} Accelerator acs:ga:{#regionId}:{#accountId}:ga/{#acceleratorId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The ID of the region where the GA instance is deployed. Set the value to cn-hangzhou.	cn-hangzhou
BandwidthPackageId	string	Yes	The ID of the bandwidth plan.	gbwp-bp1sgzldyj6b4q7cx****
AcceleratorId	string	Yes	The ID of the GA instance.	ga-bp1qe94o52ot4pkfn****

Response parameters

Parameter	Type	Description	Example
	object	The returned information.
RequestId	string	The ID of the request.	B7770CB9-9745-4FE5-9EDA-D14B01A12A50
Accelerators	array	The ID of the GA instance.
	string	The ID of the GA instance.	ga-bp1qe94o52ot4pkfn****
BandwidthPackageId	string	The ID of the bandwidth plan.	gbwp-bp1sgzldyj6b4q7cx****

Examples

Sample success responses

JSONformat

{
  "RequestId": "B7770CB9-9745-4FE5-9EDA-D14B01A12A50",
  "Accelerators": [
    "ga-bp1qe94o52ot4pkfn****"
  ],
  "BandwidthPackageId": "gbwp-bp1sgzldyj6b4q7cx****"
}

Error codes

HTTP status code	Error code	Error message	Description
400	NotExist.BandwidthPackage	The bandwidth package does not exist.	The bandwidth package does not exist.
400	StateError.BandwidthPackage	The state of bandwidth package is invalid.	The bandwidth plan is in an invalid state.
400	StateError.Accelerator	The state of the accelerated instance is invalid.	The status of the GA instance is invalid.
400	BandwidthPackageCannotUnbind.EndpointGroup	Cross-border bandwidth package cannot be unbound, because endpointGroup contains unsupported regions after unbinding.	-
400	Exist.EndpointGroup	The endpoint group already exists.	The endpoint group already exists.
500	UnknownError	An error occurred while processing your request. Please try again. If the error persists, please submit a ticket.	An error occurred while the request was being processed. Try again later.

For a list of error codes, visit the Service error codes.

Change history

Change time

Summary of changes

Operation

2023-04-13

The Error code has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	Error Codes 400 change
	delete Error Codes: 500