Why "CloudWatch Confirmation events" arrive on the Default API?

[Jonathan Ballet]

Hello,

I configured a new CloudWatch Events integration by following the documentation in Amazon CloudWatch Events Integration.

On AWS, when the a new topic subscription is created, CloudWatch automatically sends a "Confirmation Events" to Opsgenie, which creates a new alert for that.

However, although I configured the SNS topic to send the alert to the CloudWatch Event integration endpoint, with its own specific API key, the CloudWatch Confirmation event gets processed by the "Default API" integration, always.

I couldn't find any information about that in the documentation above, and there's only a slight note Tags for Built-in Alerts in the Default API Integration page.

I wanted to have a special notification policy for this specific event and I originally configured it on the CloudWatch integration, but I realized that wasn't working... Am I missing something here?

[Nick Haller]

Hi @Jonathan Ballet ,

This is how Opsgenie handles test alerts / confirmations from CloudWatch (and some other integrations) - so the connection can be tested with the actual integration processing taken out of the equation, but ensures there is a connection with Opsgenie.

Moving forward real alerts created by CloudWatch will trigger through the integration. If you see different, please let us know.