Describe the feature
ECS targets can override any item in the TaskOverride structure via the input parameter, according to the docs.
However, today, only the containerOverrides option is exposed:
|
const containerOverrides = this.props.containerOverrides && this.props.containerOverrides |
|
.map(({ containerName, ...overrides }) => ({ name: containerName, ...overrides })); |
|
const input = { containerOverrides }; |
Use Case
I need to override CPU/Memory at the Task Definition level, but CDK doesn't currently expose that option.
Proposed Solution
All input options (documented in the TaskOverride structure docs) should be allowed. Specifically, these are missing today:
cpuephemeralStorageexecutionRoleArninferenceAcceleratorOverridesmemorytaskRoleArn
Other Information
No response
Acknowledgements
CDK version used
2.168.0
Environment details (OS name and version, etc.)
Mac, Node 20 LTS
Describe the feature
ECS targets can override any item in the
TaskOverridestructure via theinputparameter, according to the docs.However, today, only the
containerOverridesoption is exposed:aws-cdk/packages/aws-cdk-lib/aws-events-targets/lib/ecs-task.ts
Lines 225 to 227 in 1b7265b
Use Case
I need to override CPU/Memory at the Task Definition level, but CDK doesn't currently expose that option.
Proposed Solution
All
inputoptions (documented in theTaskOverridestructure docs) should be allowed. Specifically, these are missing today:cpuephemeralStorageexecutionRoleArninferenceAcceleratorOverridesmemorytaskRoleArnOther Information
No response
Acknowledgements
CDK version used
2.168.0
Environment details (OS name and version, etc.)
Mac, Node 20 LTS