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
{{ message }}
This repository has been archived by the owner on Jan 4, 2024. It is now read-only.
The way that the CloudWatch logs (such as /var/log/dmesg) are configured for the hosts in ecs-cluster.yaml means that CF is not aware of them and therefore cannot delete them with the stack is deleted.
Unless they are created as resources in a CF template I am not sure that they can be deleted without adding a new helper script that is triggered on a delete stack.
A subsequent create using the same stack name will just re-use the existing log groups so this is not a high priority issue just a clean-up type thing (I think).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The way that the CloudWatch logs (such as /var/log/dmesg) are configured for the hosts in ecs-cluster.yaml means that CF is not aware of them and therefore cannot delete them with the stack is deleted.
Unless they are created as resources in a CF template I am not sure that they can be deleted without adding a new helper script that is triggered on a delete stack.
A subsequent create using the same stack name will just re-use the existing log groups so this is not a high priority issue just a clean-up type thing (I think).
The text was updated successfully, but these errors were encountered: