How to setup Alias when message gets sent from AWS SNS to Opsgenie

[叶红利]

Hi Team:

I'm struggling with new Alert gets created within Opsgenie for same SNS message.

The set up flow is:   AWS API Gateway -> AWS Lambda -> AWS SNS (through the Https of 'Incoming AWS SNS') -> Opsgenie (Integration: Incoming AWS SNS ).

Each time, I access the AWS API Gateway, new alert gets created, BUT I expect them as duplicated. 

Not sure what's the mechanism for Alias setup when AWS SNS message gets sent to Opsgenie. 

[Mubeen Mohammed]

Hello @叶红利 

Thank you for contacting the Atlassian Community!

Opsgenie has a mechanism to prevent creating duplicate alerts for the same incident. Deduplication is based on identifying unique alerts through a key parameter known as the "alias."

Setting Up Deduplication for Incoming AWS SNS:

• Configure the Alias: When setting up your Incoming AWS SNS integration in Opsgenie, you should configure the alias field to identify unique alerts. This could be a specific parameter from your SNS message that remains consistent across messages you consider duplicates.

• Use Consistent Identifiers: Ensure that the identifier parameter you use in the alias field (like a request ID or unique message attribute) is consistent for messages you want to be treated as duplicates.
  

For more detailed guidance, you can refer to the official Opsgenie documentation on alert deduplication and also refer to the community article

Plan Limitations:

• If you do not see the option to configure the alias field in your integration settings, it may be due to a plan limitation. In such cases, you will have to rely on the default alias value sent from the source (SNS message) for deduplication.

I hope the details provided are helpful.

Regards
Mubeen Mohammed
Cloud Support Engineer