Repository navigation
fix(ecs): Support 32 vCPU Fargate task definitions - #4668
Merged
kddejong merged 1 commit intoSep 1, 2026
Merged
Conversation
Add the 32768 CPU unit (32 vCPU) tier to ECS Fargate validation. E3047 (FargateCpuMemory) now accepts the supported memory values for 32 vCPU (60 GB, 120 GB, 244 GB), and E3048 (TaskFargateProperties) accepts 32768 as a valid Cpu value. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size
satyakigh
approved these changes
Sep 1, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4668 +/- ##
==========================================
+ Coverage 94.61% 94.62% +0.01%
==========================================
Files 432 432
Lines 15437 15448 +11
Branches 2995 2995
==========================================
+ Hits 14606 14618 +12
Misses 453 453
+ Partials 378 377 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available
N/A
Description of changes
Amazon ECS Fargate now supports a 32 vCPU (
32768CPU units) task size, but cfn-lint rejected it. Two rules needed updating:FargateCpuMemory): added the32768CPU tier. Per the task size docs, 32 vCPU is Linux-only and supports exactly three non-contiguous memory values — 60 GB, 120 GB, 244 GB — so the schema uses an explicit enum (61440,122880,249856MiB) plus the32 vCPU/60|120|244 GBstring forms.TaskFargateProperties): added32768(and the32 vCPUstring form) to the list of validCpuvalues.Verified end-to-end that a valid 32 vCPU Fargate task now lints clean, and invalid CPU/memory combinations still error.
Description of how you validated changes
test_ecs_fargate_cpu_memory.py(E3047) andtest_ecs_task_fargate_properties.py(E3048) covering integer, vCPU/GB string, and MiB-string forms plus an invalid-memory case.ruff checkandruff format --checkclean.Checklist
pre-commitlocally with your changes?By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.