1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi, I would start troubleshooting by checking your AWS Identity and Access Management Permissions for how you're trying to deploy the SQS Policy.
- Identity Policies for Deploying CloudFormation (Typically the User or Role you are using to deploy the CloudFormation)
- (If exists) Ensure the Queue Policy is not blocking access to deploy/update another Queue Policy.
- If in Organizations, that no SCPs are blocking SQS or any of the necessary permissions.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa