feat: Add support for ECS Express service#389
feat: Add support for ECS Express service#389bryantbiggs merged 3 commits intoterraform-aws-modules:masterfrom
Conversation
| } | ||
|
|
||
| # ECS holds on to the service names for indefinitely | ||
| # And people wonder why ECS isn't used more ¯\_(ツ)_/¯ |
There was a problem hiding this comment.
😄 One of the most stable services by AWS...
|
Caution For those who have arrived here due to issues with ECS Express, please consider the following: From a module perspective, we simply surface what is provided via the AWS APIs and make it easier to consume those services by providing the necessary components (IAM roles, permissions, security groups, cloudwatch log groups, etc.) to allow users to create the respective resources easily and efficiently via Terraform |
## [7.2.0](v7.1.0...v7.2.0) (2026-01-13) ### Features * Add support for ECS Express service ([#389](#389)) ([85161f8](85161f8))
|
This PR is included in version 7.2.0 🎉 |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
2 participants
Description
Motivation and Context
Caution
For those who have arrived here due to issues with ECS Express, please consider the following:
a. If you are experiencing issues with constant diffs, please open an issue on the AWS provider if one does not already exist. We cannot control that behavior here, and the lifecycle
ignore_changesis only a hack that ultimately is not desirable in this situation. Those changes to clean up the persistent changes within the Terraform diff need to be corrected and handled at the providerb. If you are experiencing issues with the service, please open a ticket through your AWS console/account manager or file a feature request on the containers roadmap. There are a number of deficiencies with ECS Express service (resources created outside of IaC that users cannot control through IaC, dangling/orphaned resources, dependency and ordering not respected, etc.) that users will need to surface with the ECS team in order to get those deficiencies corrected/remediated
From a module perspective, we simply surface what is provided via the AWS APIs and make it easier to consume those services by providing the necessary components (IAM roles, permissions, security groups, cloudwatch log groups, etc.) to allow users to create the respective resources easily and efficiently via Terraform
Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request