thanks @kackyt for submitting the request and volunteering for PR contribution.

Hi @kackyt - I was looking at this issue and saw that there is the containerOverrides property for the EcsRunTask. With a ContainerOverride it seems that you can override the ephemeralStorage and the cpu for an ecs task. Would this already help you/solve the issue?
For documentation reference see here: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_stepfunctions_tasks.EcsRunTask.html#containeroverrides

And here for the API reference: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html#API_RunTask_RequestSyntax

@daschaa
The method to allocate resources by overriding cpu and memory settings in ContainerOverrides is limited to using ec2 instances in ECS, while allocating resources for Fargate is not possible with ContainerOverrides, so I would like to resolve this feature.

@kackyt Thanks for the clarification! I didn‘t knew that. 👍🏼 Do you have a link to some documentation where I can find that information?

@daschaa

The task definition reference contains the following link to a description of the Fargate task.

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size

For tasks that run on Fargate (both Linux and Windows containers), this field is required and you must use one of the following values, which determines your range of supported values for the memory parameter. The table below shows the valid combinations of task-level CPU and memory.

The same applies to EcsRunTask.

Hey there I believe was already addressed by this?: 5f59787.

@VaidSaraswat
This is a feature request for EcsRunTask cpu and memory field of root parameter, not a containerOverrides issue.