1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I've successfully debugged CloudFormation errors by checking from CloudTrail which actual API call has caused the issue.
Go to event history, select Event Name from dropdown and narrow down results based on timestamp from failing event in CloudFormation stack.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Could you post an excerpt from your CloudFormation template? There's not a lot to go on here.
added the template section which creates queue and queue policy
Thanks - and what region are you using? I'd note that the best course of action here is to raise a support case because what we're doing here is trying to narrow down the cause and the support team can do that much easier.