Try to get the queue before creating it to avoid the AccessDenied error #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eate queues, i.e. queues are created manually on the DevOps side, and clients are given only read-write permissions to these queues. The previous implementation of queue registration leads to an error: ``` An error occurred (AccessDenied) when calling the CreateQueue operation: User: arn:aws:sts::*** is not authorized to perform: sqs:createqueue on resource: arn:aws:sqs:us-west-2:*** because no identity-based policy allows the sqs:createqueue action ``` To avoid this error, it is suggested to first try to get this queue and if it does not exist, create it.
|
@Bogdanp Could you please take a look on this pull-request? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are situations in which clients are limited in the rights to create queues, i.e. queues are created manually on the DevOps side, and clients are given only read-write permissions to these queues.
The previous implementation of queue registration leads to an error:
An error occurred (AccessDenied) when calling the CreateQueue operation: User: arn:aws:sts::*** is not authorized to perform: sqs:createqueue on resource: arn:aws:sqs:us-west-2:*** because no identity-based policy allows the sqs:createqueue actionTo avoid this error, it is suggested to first try to get this queue and if it does not exist, create it.
Related issue #14