feat(applicationautoscaling): add high-resolution ECS predefined metrics - #38219
Open
sanyamk23 wants to merge 3 commits into
Open
feat(applicationautoscaling): add high-resolution ECS predefined metrics#38219sanyamk23 wants to merge 3 commits into
sanyamk23 wants to merge 3 commits into
Conversation
github-actions
Bot
added
the
beginning-contributor
github-actions
Bot
added
effort/medium
aws-cdk-automation
previously requested changes
Jun 30, 2026
aws-cdk-automation
dismissed
their stale review
July 2, 2026 14:08
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
aws-cdk-automation
added
the
pr/needs-community-review
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
July 31, 2026 16:08
522340e to
b0a9ad8
Compare
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
August 2, 2026 20:10
b0a9ad8 to
1238b20
Compare
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
August 3, 2026 18:52
1238b20 to
b0a9ad8
Compare
abidhasan-aws
temporarily deployed
to
automation
August 7, 2026 11:13 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
abidhasan-aws
temporarily deployed
to
automation
August 7, 2026 11:13 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Author
|
Full CI including build is green. Ready for review. |
Author
|
Hi @otaviomacedo, I added high-resolution 1-minute ECS predefined metrics for Application Auto Scaling. Could you take a look? |
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
August 17, 2026 12:19
97c8392 to
53794fc
Compare
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
August 17, 2026 19:46
53794fc to
ebe7aac
Compare
…ross-repo PRs When the GitHub API returns a 404 for the list reviews endpoint (which can happen for cross-repo PRs from forks or when the PROJEN_GITHUB_TOKEN lacks access to the source repository), treat it as no existing reviews rather than crashing the entire validate-pr job. Previously, the 404 error would propagate up to run().catch() in index.ts, causing the process to exit with code 1 and failing the workflow.
Add ECS_SERVICE_AVERAGE_CPU_UTILIZATION_HIGH_RESOLUTION and ECS_SERVICE_AVERAGE_MEMORY_UTILIZATION_HIGH_RESOLUTION to the PredefinedMetric enum, enabling target-tracking scaling policies that use 20-second metric reporting for faster auto scaling. closes aws#38207
…n ECS metrics Add integration test and snapshot verifying that ECS high-resolution (20-second) predefined metrics for CPU and memory utilization can be used in target tracking scaling policies.
sanyamk23
force-pushed
the
feat/add-high-resolution-ecs-metrics
branch
from
August 17, 2026 19:57
ebe7aac to
cec77ec
Compare
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
4 participants
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.
Motivation
Closes #38207
Amazon ECS now supports high-resolution (20-second) metrics for faster auto scaling, but the CDK
PredefinedMetricenum inaws-applicationautoscalingis missing the corresponding high-resolution variants. This forces users to use error-prone string literals when authoring high-resolution target-tracking policies.Changes
Added two new members to the
PredefinedMetricenum:PredefinedMetricTypeECS_SERVICE_AVERAGE_CPU_UTILIZATION_HIGH_RESOLUTIONECSServiceAverageCPUUtilizationHighResolutionECS_SERVICE_AVERAGE_MEMORY_UTILIZATION_HIGH_RESOLUTIONECSServiceAverageMemoryUtilizationHighResolutionEach new member includes JSDoc with a
@seelink to the ECS high-resolution scaling guide.README
Added a new section under ECS Service Auto Scaling showing how to create a
ScalableTargetand attach high-resolution tracking policies, with a note about the two-step constraint for existing services.Tests
Added two unit tests verifying that each new metric value is rendered correctly in the synthesized
AWS::ApplicationAutoScaling::ScalingPolicytemplate.Testing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.