1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
If you're trying to check for some existing resources into CF, it is unfortunately not available. Instead you can use conditions and control the resource creation. For log groups in the first iteration you could delete the log group and provision the stack, from the next iteration it would be update operation so there would be no issues.
con risposta 9 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa