1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Nevermind .. I was able to overcome this. If this helps anyone:
The "Events" list of this stack was not helpful but the error came from a nested/embedded stack creation.
I was able to click on the corresponding stack in the "resources" tab and in turn look at the list of all events in that stack creation -- and spot the detailed error events there.
It turns out there was a validation error on the LENGTH of a value that ended up becoming too long (longer than 64 characters) as it was constructed using the stack name I supplied appended with some other strings.
I simply had to use a shorter name for my stack and it worked :)
Turned out to be a rather trivial issue in the end.
con risposta 5 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa