2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
To troubleshoot what has happened, you need to go to the cloudformation stack, look at Events tab and trace the first failed event that has triggered the rollback. There might be a number of reasons why a stack might fail :
- there is an outdated reference in the stack
- you do not have permissions or access to certain resources mentioned in the stack
- deployment might have failed by incident for one of the resources
- etc.
1
[Update] I have run the same stack in us-east-1 with success and using these parameters. Please note that I used t3 instances for test. So the stack does not have any issues in deployment. You need to look at the Events tab and trace the error.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- Réponse acceptéedemandé il y a 2 ans
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Please set the answer to Accepted answer if you feel that it provided the response to your query. Thanks.