Support CapacityProviderStrategy in aws_cloudwatch_event_target with ecs_target

[mgreen-sm]

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

CloudWatch / EventBridge provides the option to specify the Capacity Provider Strategy in an ECS Task target, which is currently not supported in Terraform.

The feature is useful to override the Default Capacity Provider in an ECS cluster.

New or Affected Resource(s)

• aws_cloudwatch_event_target

Potential Terraform Configuration

resource "aws_cloudwatch_event_target" "ecs_scheduled_task" {
...

  ecs_target {
     // Must not be 'EC2' or 'FARGATE' when capacity_provider_strategy is specified
    launch_type = ""
    
    ...
    
    capacity_provider_strategy {
      capacity_provider = "example_capacity_provider_one"
      weight = 1
      base   = 0
    }

    capacity_provider_strategy {
      capacity_provider = "example_capacity_provider_two"
      weight = 1
      base   = 0
    }

  }

...
}

References

• aws_cloudwatch_event_target support explicit capacity provider strategy for ecs_target EC2 #17185
• Support EnableExecuteCommand attribute in cloudwatch_event_target with ecs_target #19949
• Release v1.38.66 aws/aws-sdk-go#3974
• https://aws.amazon.com/about-aws/whats-new/2021/07/amazon-ecs-supports-additional-configurations-for-scheduled-and-event-driven-tasks/
• https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_EcsParameters.html#eventbridge-Type-EcsParameters-PropagateTags

[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.