New resource to manage load balancer attachment for ECS services

[syskill]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Now that the load balancers for an ECS service can be updated without destroying and re-creating the service (cf. #23596), it would be nice to have a separate resource to manage this association for a pre-existing ECS service, along the lines of aws_lb_target_group_attachment and aws_autoscaling_attachment.

New or Affected Resource(s)

• aws_ecs_service_attachment

Potential Terraform Configuration

resource "aws_ecs_service_attachment" "example" {
  service_name     = data.aws_ecs_service.my_mongo.service_name 
  target_group_arn = aws_lb_target_group.example.arn
  container_name   = "mongo"
  container_port   = 8080
} 

The user should be able to specify either target_group_arn for an Application Load Balancer, or elb_name for a Classic Load Balancer.

If the ECS service is managed by other Terraform code, then its aws_ecs_service resource would need a lifecycle block to ignore changes to load_balancer configuration.

References

• r/aws_ecs_service: update propagate_tags enable_ecs_managed_tags load_balancer and service_registries without destroy & recreate #23600
• r/aws_ecs_service: fix load_balancer & service_registries to update without destroy & recreate #23786

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.