Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to set priority in AWS SNS


Hello, I would like to know how it is possible to set the priority using message's attribute in Opsgenie through the integration with AWS through SNS.

I have tried the following code:

"MessageAttributes": {
"teams": {"Type": "String", "Value": "TeamA"},
"alias": {"Type": "String", "Value": "myAlias"},
"eventType": {"Type": "String", "Value": "create"},
"priority": {"Type": "String", "Value": "P1"},
"tags": {"Type": "String", "Value": "RDS"}
All the fields work except the priority one that assigns always P3 by default or not found mapping value, any idea?

I checked out documentation but nothing useful :(

Thank u

2 answers

1 vote
Nick H Atlassian Team Sep 29, 2022

Related more in depth article on how this can be done as well:

How to Map Alert Priorities in Opsgenie

1 vote
Nick H Atlassian Team Jun 17, 2020

Hi @Jose_Martin ,

Thanks for reaching out. This similar community post may help with your issue:

^ Although related to Solarwinds, the concept is the same. AWS's priority might vary from Opsgenie's so it will not map 1-to-1.

Depending on which field (like the Subject, AlarmDescription, etc.) the AWS priority is being parsed in, multiple Create Alert actions can be added to the integration that filter on this -> then map to the corresponding Opsgenie priority.




If you have any additional details, screenshots, examples, etc. of your AWS alerts defaulting to P3s, I could provide some more suggestions. Let us know, or if this helps!



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events