Repository navigation
fix(E3615): Allow a CloudWatch alarm Period of 20 - #4905
Merged
kddejong merged 1 commit intoOct 27, 2026
Merged
Conversation
kddejong
approved these changes
Oct 26, 2026
E3615 rejected Period: 20 on AWS::CloudWatch::Alarm. CloudWatch accepts 20 seconds for high-resolution alarms: the AWS::CloudWatch::Alarm reference lists the valid values as 10, 20, 30, 60 and any multiple of 60, and the PutMetricAlarm API reference also allows 20. Add 20 to the enum in aws_cloudwatch_alarm/period.json and to the rule's description and message. Values such as 15 and 45 are still reported. Fixes aws-cloudformation#4835
kddejong
force-pushed
the
fix/e3615-period-20
branch
from
October 26, 2026 20:52
3346ba7 to
4195285
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4905 +/- ##
=======================================
Coverage 94.68% 94.68%
=======================================
Files 441 441
Lines 16067 16067
Branches 3116 3116
=======================================
Hits 15213 15213
Misses 470 470
Partials 384 384
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:
Fixes #4835
Description of changes:
E3615 rejected
Period: 20onAWS::CloudWatch::Alarm. The AWS::CloudWatch::Alarm reference lists 10, 20, 30, 60 and any multiple of 60 as valid, and the PutMetricAlarm API reference also allows 20. This adds 20 to the enum inperiod.jsonand to the rule's description and message. Values like 15 and 45 are still reported. The unit tests now cover 20 as an integer and as a string. The rule tests and pre-commit pass, and the full suite shows no new failures.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.