All Products
Search

This Product

    ApsaraDB RDS:DeleteADSetting

    Document Center

    ApsaraDB RDS:DeleteADSetting

    Last Updated:Apr 28, 2024

    Deletes an ApsaraDB RDS for SQL Server instance from an Active Directory (AD) domain.

    Operation description

    Supported database engines

    • SQL Server

    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
    rds:DeleteADSettingWrite
    • DBInstance
      acs:rds:{#regionId}:{#accountId}:dbinstance/{#DbInstanceId}
      none
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    ClientTokenstringNo

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

    		ETnLKlblzczshOTUbOCz*****
    DBInstanceIdstringYes

    The instance ID. You can call the DescribeDBInstances operation to query the instance ID.

    		rm-bp1k8s41l2o52****
    RegionIdstringYes

    The ID of the region.

    		cn-hangzhou

    Response parameters

    ParameterTypeDescriptionExample
    object

    The response parameters.

    RequestIdstring

    The ID of the request.

    		1AD222E9-E606-4A42-BF6D-8A4442913CEF

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "1AD222E9-E606-4A42-BF6D-8A4442913CEF"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400EngineNotSupportedThe engine does not support the operation.The operation is not supported for the database engine that is run on the RDS instance.
    400EngineVersionNotSupportedEngineVersion specified cannot be replicate with the source DB Instance.Instance cloning is not supported for the database engine version of the current instance.
    400InvalidInstanceNodeType.NotFoundThe specified NodeType is not found.-
    400InvalidShareDbInstanceClassNotSupportThe current instance classType is not support operation.This operation is not supported for the specified instance type.
    400IncorrectEngineVersionCurrent DB instance engine version does not support this operation.This operation is not supported for the database engine version of the current instance.
    403InvalidOperation.InvalidCurrent instance is not in Domain, remove operation is only valid when current instance is in domain.-
    403IncorrectDBInstanceStateCurrent DB instance state does not support this operation.-
    403ClusterTypeErrorCustins Cluster Type Error, Support User ClusterThe Custins cluster type is invalid. Only the user cluster type is supported.
    404InvalidDBInstanceName.NotFoundInvalid DBInstanceId NotFound.The instance ID cannot be found.
    404InvalidDBInstance.NotFoundSpecified instance does not exist or not support.The RDS instance cannot be found, is deleted, or does not support the operation.

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

    Change history

    Change timeSummary of changesOperation
    2023-01-11The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
      delete Error Codes: 403
      delete Error Codes: 404
    2022-06-13Add Operationsee changesets