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 action
To avoid this error, it is suggested to first try to get this queue and if it does not exist, create it.
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 action
To avoid this error, it is suggested to first try to get this queue and if it does not exist, create it.Related issue #14