ecs: Unclear requirement for Fargate Windows task-level CPU/Memory properties

[Abogical]

Describe the issue

According to the ECS docs, Windows Fargate tasks ignore the required CPU and memory properties. However, this is not strictly true as Fargate internally uses those properties to set its instance type and memory. They are just not strictly enforced as Windows doesn't have a native mechanism similar to cgroups that can easily enforce collective resource limits on a group of containers.

ECS will soon update the docs to note this behavior. We should update the CDK docs to reflect this as soon as this update is published.

Publishing this on behalf of @Yogagh (commented here)

Links

• https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ecs.FargateTaskDefinition.html#cpu
• https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ecs.FargateTaskDefinition.html#memorylimitmib

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.