2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
After running a few experiments, it does appear as if the order is being preserved, the issue is that there is a delay from the invocation of the lambda, it finished, and then wrote to the logs. No surprise, but writing is not immediate.
This delay is causing the log group to be recreated. I am finding that if I impose an artificial delay between the invocation and the deletion of the log group, the stack gets cleaned up appropriately.
Edited by: lsitzman on Apr 1, 2020 8:07 AM
con risposta 4 anni fa
0
Another way to solve this is to take away the permission from the execution role to create a log group (logs:CreateLogGroup
), but only if you don't care about logs produced by the Delete event.
con risposta 9 mesi fa
Contenuto pertinente
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Could you please share more details on how you resolved this issue? How did you implement that artificial delay?