Releases an expired Anti-DDoS Pro or Anti-DDoS Premium instance.

If an Anti-DDoS Pro or Anti-DDoS Premium instance expires, DDoS mitigation stops. The instance stops forwarding service traffic seven days after it expires.

  • We recommend that you renew your instance before it expires. This eliminates the impacts on service protection and traffic forwarding. You can call the DescribeInstances operation to query the expiration time of all instances. If you want to renew your instance, log on to the Anti-DDoS Pro console.
  • If you do not plan to renew your instance, switch the service traffic back to the origin sever before your instance expires. To switch the traffic back, change the service IP address to the IP address of the origin server or modify the CNAME to stop forwarding service traffic to Anti-DDoS Pro or Anti-DDoS Premium. This prevents service interruptions caused by the expiration.

You can call this operation to release an instance after the instance expires.

Note Before you release an instance, make sure that the service traffic is switched to the origin server.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes ReleaseInstance

The operation that you want to perform. Set the value to ReleaseInstance.

InstanceId String Yes ddoscoo-cn-mp91j1ao****

The ID of the instance that you want to release.

Note You can release only expired instances. You can call the DescribeInstances operation to query the IDs and expiration status of all instances.
RegionId String Yes cn-hangzhou

The region ID of the instance. Valid values:

  • cn-hangzhou: mainland China, which indicates an Anti-DDoS Pro instance. This is the default value.
  • ap-southeast-1: outside mainland China, which indicates an Anti-DDoS Premium instance.

All Alibaba Cloud API operations must include common request parameters. For more information about common request parameters, see Common parameters.

For more information about sample requests, see the Examples section of this topic.

Response parameters

Parameter Type Example Description
RequestId String 0bcf28g5-d57c-11e7-9bs0-d89d6717dxbc

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=ReleaseInstance
&InstanceId=ddoscoo-cn-mp91j1ao****
&RegionId=cn-hangzhou
&<Common request parameters>

Sample success responses

XML format

<ReleaseInstanceResponse>
	  <RequestId>0bcf28g5-d57c-11e7-9bs0-d89d6717dxbc</RequestId>
</ReleaseInstanceResponse>

JSON format

{
  "RequestId": "0bcf28g5-d57c-11e7-9bs0-d89d6717dxbc"
}

Error codes

For a list of error codes, visit the API Error Center.