Composite alarm rules require ARN format, not alarm names

warning

configurationUpdated Nov 11, 2024(via Exa)

Sources

Cloudwatch: add basic composite alarm support · Pull Request #11828 · localstack/localstackgithub.com

Technologies:

LocalStacksubject

Amazon CloudWatchAmazon CloudWatch metrics correlate with this issue and help confirm diagnosis

How to detect:

Composite alarm rules in LocalStack currently support only ARN-based alarm references. Using alarm names instead of ARNs will cause alarm rule evaluation to fail or be skipped.

Recommended action:

Use fully qualified ARN format in composite alarm rules: ALARM("arn:<partition>:cloudwatch:<region>:account-id:alarm:<alarm-name>"). Construct ARNs programmatically if creating alarms dynamically. Do not use shorthand alarm name references.