How do we look up more verbose information by RequestID's thrown in AWS CloudFormation events which status reports CREATE_FAILED?

0

Without setting up a CloudTrail and executing a CFN template which rolls back, I have started looking at Debugging options. I found this which says we can see the most recent without a created trail.

I tried to find RequestId documentation from here entering 'requested' in the search bar, which returned many unrelated items to my specific case (thanks for the attempt Kendra:).

I also have looked at cli docs here

I guess I fist need to know what a RequestID is capable of helping me trace, as I am doing a simple debug of an instance I already know that has the wrong AMI ID for that region, but am trying. to re-familiarize myself. with fixing CFN templates after being out of the loop for a few years.

I'd like to know how someone else handles a CREATE _FAILED and ways to use the status reason in a verbose way. Each reason appears to be ';' separated, so even just a point in that direction might help weed through the mountain of information here. Thanks ahead of time- Rudy

Keine Antworten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen