All Products
Search
Document Center

Anti-DDoS:ReleaseInstance

Last Updated:Nov 11, 2025

Release an expired Anti-DDoS Proxy instance.

Operation description

After an Anti-DDoS instance expires, it stops providing DDoS attack protection services. Seven days after expiration, it stops forwarding service traffic.

  • We recommend that you renew your instance before it expires to avoid impacts on service protection and forwarding. You can call DescribeInstances to query the expiration time of an instance. To renew the instance, go to the Anti-DDoS console to perform the operation.

  • If you do not plan to renew the instance, we recommend that you restore the protected service IP (no longer use the Anti-DDoS IP as the service IP) or service DNS parsing (no longer parse service traffic to the CNAME address of Anti-DDoS) before the Anti-DDoS instance expires. This prevents service traffic from being forwarded to the Anti-DDoS instance and avoids disruption to normal service forwarding when the instance expires.

After the instance expires, you can call this operation to release the specified Anti-DDoS instance.

Note

Before releasing the specified instance, ensure that you have restored the protected service IP or service DNS parsing.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

yundun-ddoscoo:ReleaseInstance

update

*All Resource

*

None

None

Request parameters

Parameter

Type

Required

Description

Example

InstanceId

string

Yes

The ID of the instance to be released.

Note

Only expired instances can be released. You can call DescribeInstances to query the IDs and expiration status of all Anti-DDoS Proxy instances.

ddoscoo-cn-mp91j1ao****

Response elements

Parameter

Type

Description

Example

object

RequestId

string

The ID of the request. This is a unique identifier generated by Alibaba Cloud for the request. You can use it to troubleshoot and locate issues.

06FFAF5F-CD3E-4886-A849-AAB40DFF6515

Examples

Success response

JSON format

{
  "RequestId": "06FFAF5F-CD3E-4886-A849-AAB40DFF6515"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.