RAM / Client / disassociate_resource_share_permission

disassociate_resource_share_permission

RAM.Client.disassociate_resource_share_permission(**kwargs)

Removes a managed permission from a resource share. Permission changes take effect immediately. You can remove a managed permission from a resource share only if there are currently no resources of the relevant resource type currently attached to the resource share.

See also: AWS API Documentation

Request Syntax

response = client.disassociate_resource_share_permission(
    resourceShareArn='string',
    permissionArn='string',
    clientToken='string'
)

Parameters:

• resourceShareArn (string) –

  [REQUIRED]

  The Amazon Resource Name (ARN) of the resource share that you want to remove the managed permission from.

• permissionArn (string) –

  [REQUIRED]

  The Amazon Resource Name (ARN) of the managed permission to disassociate from the resource share. Changes to permissions take effect immediately.

• clientToken (string) –

  Specifies a unique, case-sensitive identifier that you provide to ensure the idempotency of the request. This lets you safely retry the request without accidentally performing the same operation a second time. Passing the same value to a later call to an operation requires that you also pass the same value for all other parameters. We recommend that you use a UUID type of value..

  If you don’t provide this value, then Amazon Web Services generates a random one for you.

  If you retry the operation with the same ClientToken, but with different parameters, the retry fails with an IdempotentParameterMismatch error.

Return type:

dict

Returns:

Response Syntax

{
    'returnValue': True|False,
    'clientToken': 'string'
}

Response Structure

• (dict) –

  • returnValue (boolean) –

    A return value of true indicates that the request succeeded. A value of false indicates that the request failed.

  • clientToken (string) –

    The idempotency identifier associated with this request. If you want to repeat the same operation in an idempotent manner then you must include this value in the clientToken request parameter of that later call. All other parameters must also have the same values that you used in the first call.

Exceptions

• RAM.Client.exceptions.MalformedArnException

• RAM.Client.exceptions.UnknownResourceException

• RAM.Client.exceptions.InvalidParameterException

• RAM.Client.exceptions.InvalidClientTokenException

• RAM.Client.exceptions.ServerInternalException

• RAM.Client.exceptions.ServiceUnavailableException

• RAM.Client.exceptions.OperationNotPermittedException

• RAM.Client.exceptions.InvalidStateTransitionException