add_permission
(**kwargs)¶Adds a permission to a queue for a specific principal. This allows sharing access to the queue.
When you create a queue, you have full control access rights for the queue. Only you, the owner of the queue, can grant or deny permissions to the queue. For more information about these permissions, see Allow Developers to Write Messages to a Shared Queue in the Amazon SQS Developer Guide .
Note
AddPermission
generates a policy for you. You can use SetQueueAttributes
to upload your policy. For more information, see Using Custom Policies with the Amazon SQS Access Policy Language in the Amazon SQS Developer Guide .AddPermission
, RemovePermission
, and SetQueueAttributes
actions in your IAM policy.Some actions take lists of parameters. These lists are specified using the param.n
notation. Values of n
are integers starting from 1. For example, a parameter list with two elements looks like this:
&AttributeName.1=first
&AttributeName.2=second
Note
Cross-account permissions don't apply to this action. For more information, see Grant cross-account permissions to a role and a user name in the Amazon SQS Developer Guide .
See also: AWS API Documentation
Request Syntax
response = queue.add_permission(
Label='string',
AWSAccountIds=[
'string',
],
Actions=[
'string',
]
)
[REQUIRED]
The unique identification of the permission you're setting (for example, AliceSendMessage
). Maximum 80 characters. Allowed characters include alphanumeric characters, hyphens ( -
), and underscores ( _
).
[REQUIRED]
The Amazon Web Services account numbers of the principals who are to receive permission. For information about locating the Amazon Web Services account identification, see Your Amazon Web Services Identifiers in the Amazon SQS Developer Guide .
[REQUIRED]
The action the client wants to allow for the specified principal. Valid values: the name of any action or *
.
For more information about these actions, see Overview of Managing Access Permissions to Your Amazon Simple Queue Service Resource in the Amazon SQS Developer Guide .
Specifying SendMessage
, DeleteMessage
, or ChangeMessageVisibility
for ActionName.n
also grants permissions for the corresponding batch versions of those actions: SendMessageBatch
, DeleteMessageBatch
, and ChangeMessageVisibilityBatch
.
None