Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cloudwatch] Alarms don't execute on KMS encrypted SNS #11121

Closed
du291 opened this issue Oct 26, 2020 · 3 comments
Closed

[cloudwatch] Alarms don't execute on KMS encrypted SNS #11121

du291 opened this issue Oct 26, 2020 · 3 comments
Labels
@aws-cdk/aws-cloudwatch Related to Amazon CloudWatch bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/small Small work item – less than a day of effort good first issue Related to contributions. See CONTRIBUTING.md p1

Comments

@du291
Copy link

du291 commented Oct 26, 2020

Alarms do not seem to execute properly when configured to a Topic with master_key.

Reproduction Steps

topic = aws_sns.Topic(self.stack, 'alarm-topic',
                              display_name='Topic for alarms',
                              master_key=key,
                              topic_name=self.alarms_topic_name)
alarm.add_alarm_action(aws_cloudwatch_actions.SnsAction(alarms_topic))

then trigger the alarm via boto3 set_alarm_state

What did you expect to happen?

Triggering the alarm would send notification to the topic.

What actually happened?

The following error on aws cloudwatch alarm page:

Failed to execute action arn:aws:sns:eu-west-1:461491260158:rivendell-eu-west-1-log-test-pht-alarms-topic. Received error: "null (Service: AWSKMS; Status Code: 400; Error Code: AccessDeniedException; Request ID: 4fea0cd9-2182-432e-a0a0-5442996cc605; Proxy: null)"

Environment

CLI Version : 1.70
Framework Version: Python 3.8.5
Node.js Version: v14.11.0
OS : Linux
Language (Version): Python (3.8.5)

Other


This is 🐛 Bug Report

@du291 du291 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Oct 26, 2020
@SomayaB SomayaB changed the title [aws_cloudwatch] Alarms don't execute on KMS encrypted SNS [cloudwatch] Alarms don't execute on KMS encrypted SNS Oct 26, 2020
@github-actions github-actions bot added the @aws-cdk/aws-cloudwatch Related to Amazon CloudWatch label Oct 26, 2020
@rix0rrr rix0rrr added effort/small Small work item – less than a day of effort good first issue Related to contributions. See CONTRIBUTING.md p1 labels Nov 2, 2020
@rix0rrr
Copy link
Contributor

rix0rrr commented Nov 2, 2020

I would think that the key needs a permission added to have the CloudWatch service principal be able to encrypt using it.

@SomayaB SomayaB removed the needs-triage This issue or PR still needs to be triaged. label Nov 2, 2020
@S3ky
Copy link

S3ky commented Apr 1, 2021

Hi @rix0rrr, @jumi-dev,

I saw, that you have the open PR for that issue (#12117), but there are some changes requested. Could you please take a look at it?

Thank ou.

@github-actions
Copy link

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-cloudwatch Related to Amazon CloudWatch bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/small Small work item – less than a day of effort good first issue Related to contributions. See CONTRIBUTING.md p1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants