Repository navigation
Conversation
The ECS hosts never got a new AMI or launch template settings: the group used the template's "$Latest", so a new template version didn't change the group and nothing started an instance refresh. A refresh started by hand skipped every host running tasks, since managed termination protection protects them from scale-in and the refresh ignored protected hosts by default. The dev hosts still run their April 2026 AMI. Point the group at the template's latest_version, so a new template starts the refresh, and refresh the protected hosts too, launching each new host before the old one goes (min 100%, max 200% healthy) and skipping hosts already on the template. managed_draining, the default for these capacity providers, is set explicitly: ECS moves a host's tasks and drains them from the load balancer before it terminates. The first apply changes the group's template version and so replaces every host, picking up the current ECS AMI and the template's metadata options.
Terraform Run Output 🤖Format and Style 🖌
|
| Pusher | @aagbsn |
| Action | pull_request |
| Environment | dev |
| Workflow | .github/workflows/check_terraform.yml |
| Last updated | Thu, 12 Nov 2026 09:28:33 GMT |
LDiazN
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ECS hosts never got a new AMI or launch template settings: the group used the template's "$Latest", so a new template version didn't change the group and nothing started an instance refresh.
Point the group at the template's latest_version, so a new template starts the refresh, and refresh the protected hosts too, launching each new host before the old one goes (min 100%, max 200% healthy) and skipping hosts already on the template.
Managed_draining, the default for these capacity providers, is set explicitly: ECS moves a host's tasks and drains them from the load balancer before it terminates.