-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Repeatable #2
Comments
I am facing the same issue! Be nice to know what the issue is. |
+1 |
I have managed to work around the problem for now,
But the clincher seems to be removing the
This is not ideal because the Cluster Name is no longer predictable, and is harder to use from my evolving, but independant deploy scripts... |
Thank you for reporting this. You are correct that this is related to the ClusterName parameter. The ECS/CloudFormation teams are aware and working on a fix. |
Any updates on how it's going? :) |
Thanks again for reporting this. I believe this has now been resolved by the CloudFormation team. I have tested by:
If you're still having problems, please re-open this issue. |
Added CloudWatch Unified Agent Removed CloudWatch Logs (only) Agent Added SSM and CWAgent managed policies to ECS Role Added ECS CloudWatch Parameter Default Logs: unchanged from previous CloudWatch Logs Agent implementation Default Metrics: Root Volume % used, Memory % Used
Same exact problem, newest version of this repository. |
I may well be doing something wrong,
but I cannot invoke the Stack creation twice with the same name.
That is:
I can't for the life of me find any dangling resources which may still be present.
This is the error message in the Cloudformation Events tab:
Any Ideas?
The text was updated successfully, but these errors were encountered: