DetachControlPolicy-阿里云帮助中心

Operation description

After you detach an access control policy, the operations performed on resources by using members are not limited by the policy. Make sure that the detached policy meets your expectations. Otherwise, your business may be affected.

Both the system and custom access control policies can be detached. If an object has only one access control policy attached, the policy cannot be detached.

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

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter	Type	Required	Description	Example
PolicyId	string	Yes	The ID of the access control policy.	cp-jExXAqIYkwHN****
TargetId	string	Yes	The ID of the object from which you want to detach the access control policy. Access control policies can be attached to the following objects: Root folder Subfolders of the Root folder Members	fd-ZDNPiT****

Response elements

Element	Type	Description	Example
	object	The returned result.
RequestId	string	The ID of the request.	9EA4F962-1A2E-4AFE-BE0C-B14736FC46CC

Examples

Success response

JSON format

{
  "RequestId": "9EA4F962-1A2E-4AFE-BE0C-B14736FC46CC"
}

Error codes

HTTP status code	Error code	Error message	Description
400	NotSupport.DetachLastControlPolicy	It is not detach the last control policy on the target node.
404	EntityNotExists.Target	The specified target does not exist in the resource directory.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.