feat(stepfunctions-tasks): allow EcsRunTask on fargate and ec2 to set capacity provider strategy

[go-to-k]

Issue # (if applicable)

Closes #20013 #30171 #7967

Reason for this change

The capacity provider strategy can't be set on EcsRunTask with EcsFargateLaunchTargetOptions and EcsEc2LaunchTargetOptions.

[capacityProviderStrategy](https://docs.aws.amazon.com/ja_jp/AmazonECS/latest/APIReference/API_RunTask.html#API_RunTask_RequestSyntax)
The capacity provider strategy to use for the task.

If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for the cluster is used.

When you use cluster auto scaling, you must specify capacityProviderStrategy and not launchType.

A capacity provider strategy can contain a maximum of 20 capacity providers.

https://docs.aws.amazon.com/ja_jp/AmazonECS/latest/APIReference/API_RunTask.html

Description of changes

This PR adds a new property capacityProviderOptions (CapacityProviderOptionsBase class with static factory methods as an enum-like class) in the target options.

The CapacityProviderOptionsBase has following sub types:

• NoCapacityProviderOptions
• CustomCapacityProviderOptions
• DefaultCapacityProviderOptions

The NoCapacityProviderOptions creates the original settings with LaunchType (EC2 or FARGATE). It is a default value for the capacityProviderOptions.

The CustomCapacityProviderOptions allows users to set the capacity provider strategy without LaunchType.

The DefaultCapacityProviderOptions allows users to use the cluster's default capacity provider strategy. The default strategy can be set by specifying no options (LaunchType and CapacityProviderStrategy) in CFn.

Describe any new or updated permissions being added

Description of how you validated changes

Both unit tests and integ tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[go-to-k]

Because amd64 is used for cpu architecture in integ tests.

If this option is not specified, running the tests on Mac will result in an error during state machine execution.