All Products
Search
Document Center

Lindorm:ReleaseLindormInstance

Last Updated:Oct 30, 2025

Releases a Lindorm instance.

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

lindorm:ReleaseLindormInstance

delete

*Instance

acs:lindorm:{#regionId}:{#accountId}:instance/{#InstanceId}

None None

Request parameters

Parameter

Type

Required

Description

Example

InstanceId

string

Yes

The ID of the instance. To obtain the instance ID, call the GetLindormInstanceList operation.

ld-bp1z3506imz2f****

Immediately

boolean

No

Specifies whether to release the instance immediately. The default value is false. If this parameter is set to false, the instance data is retained for 7 days before it is deleted. If this parameter is set to true, the instance data is deleted immediately.

false

Response elements

Element

Type

Description

Example

object

RequestId

string

The request ID.

F67BFFF3-F5C2-45B5-9C28-6E4A1E51****

Description

Examples

Success response

JSON format

{
  "RequestId": "F67BFFF3-F5C2-45B5-9C28-6E4A1E51****"
}

Error codes

HTTP status code

Error code

Error message

Description

400 ChargeType.IsNotValid The charge type is invalid. The specified charge type is invalid.
400 Instance.IsNotPostPay The instance billing type is not pay as you go.
400 Instance.DeleteProtection Instance deletion is protected. Please disable delete protection before deleting the instance. If the instance has deletion protection enabled, disable deletion protection before deleting the instance.
403 API.Forbidden The API operation is forbidden in this environment. This operation is not supported in the current environment.
403 Lindorm.Errorcode.OperationDenied You are not authorized to operate on the specified resource. You are not authorized to manage the specified resource.
403 Lindorm.Errorcode.ServiceLinkedRoleNoPermission No permission to create service linked role. You are not authorized to create the service-linked role.
404 Lindorm.Errorcode.InstanceNotFound The instance is not found. The specified instance does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.