All Products
Search
Document Center

ApsaraDB for MongoDB:DeleteDBInstance

Last Updated:Mar 15, 2024

Releases an ApsaraDB for MongoDB instance.

Operation description

Before you call this operation, make sure that the instance meets the following requirements

  • The instance is in the Running state.
  • The billing method of the instance is pay-as-you-go.
Note After an instance is released, all data in the instance is cleared and cannot be recovered. Proceed with caution.

Debugging

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

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.
OperationAccess levelResource typeCondition keyAssociated operation
dds:DeleteDBInstanceWRITE
  • DBInstance
    acs:dds:{#regionId}:{#accountId}:dbinstance/{#dbInstanceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DBInstanceIdstringYes

The instance ID.

dds-bpxxxxxxxx
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must ensure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.

ETnLKlblzczshOTUbOCzxxxxxxxxxx

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

72651AF9-7897-41A7-8B67-6C15C7F26A0A

Examples

Sample success responses

JSONformat

{
  "RequestId": "72651AF9-7897-41A7-8B67-6C15C7F26A0A"
}

Error codes

HTTP status codeError codeError messageDescription
400ChargeTypeViolationThe operation is not permitted due to charge type of the instance. -
403InstanceReleaseProtectionThe operation is not permitted due to instance release protection.The operation cannot be performed because release protection is enabled for the instance. To release the instance, disable release protection for the instance first.

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

Change history

Change timeSummary of changesOperation
2023-12-07The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 403