(ecs): Incorrect ECS Fargate cpu/memory settings are not detected

[watany-dev]

Describe the bug

Now this setting succeeds, but this is the wrong cpu/memory ratio for a Fargate setting.
It may be necessary to add a checkFargateWindowsBasedTasksSize type of determination method to Fargate as well!

    const taskDefinitiongraviton2 = new ecs.FargateTaskDefinition(this, 'TaskDefGraviton2', {
      runtimePlatform: {
        operatingSystemFamily: ecs.OperatingSystemFamily.LINUX,
        cpuArchitecture: ecs.CpuArchitecture.ARM64,
      },
      cpu: 256,
      memoryLimitMiB: 122880
    });

Expected Behavior

Before cdk synth, CDK will determine the wrong configuration.

Current Behavior

Generate unsuccessful task definitions as CFn templates

Reproduction Steps

Here's the sample code I wrote above

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.41.1

Framework Version

No response

Node.js Version

any

OS

any

Language

Typescript

Language Version

No response

Other information

No response

[peterwoodworth]

It would be nice to detect this before deployment. Do you know where we can read documentation on the exact specifications for these inputs?

[watany-dev]

The three links given in the PR below are helpful. Allowable values ​​in the 1st line, you can see whether or not there is a runtime constraint in the 2nd and 3rd lines

#22209

[watany-dev]

It is also possible to define the CPU corresponding to memory as an enum, or vice versa. However, it is assumed that it is necessary to allow ″type number″ when considering backward compatibility. Therefore, the value check process is recognized with higher priority.

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

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