You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using cloudformation/cfn-resource-provider.yaml as a nested stack in another CF Template. When that stack fails to deploy, the log group is not cleaned up.
My best guess is that this is the cause. Specifically the Log Group is destroyed while another lambda is still running. When it completes, it logs messages which (due to its permissions) recreate the log.
This seems to be resolved by revoking logs:CreateLogGroup (since CF handles the create anyway) e.g. by reducing the logs permissions from logs:* to:
- logs:CreateLogStream
- logs:PutLogEvents
The log is created and completely deleted. I've tried it twice both ways in an effort to confirm.
EDIT: It's also possible (but untested) that reversing the DependsOn (so the lambda is deleted before the Log Group) would be adequate.
The text was updated successfully, but these errors were encountered:
We're using
cloudformation/cfn-resource-provider.yaml
as a nested stack in another CF Template. When that stack fails to deploy, the log group is not cleaned up.My best guess is that this is the cause. Specifically the Log Group is destroyed while another lambda is still running. When it completes, it logs messages which (due to its permissions) recreate the log.
This seems to be resolved by revoking
logs:CreateLogGroup
(since CF handles the create anyway) e.g. by reducing the logs permissions fromlogs:*
to:The log is created and completely deleted. I've tried it twice both ways in an effort to confirm.
EDIT: It's also possible (but untested) that reversing the
DependsOn
(so the lambda is deleted before the Log Group) would be adequate.The text was updated successfully, but these errors were encountered: