You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
Please let me know the list of endpoints the OEC connects to, so that I could open the relevant firewall rules from internal network.
Apart from Opsgenie api url, I could see, OEC tries to connect to aws sqs service url in eu-central-1( https://sqs.eu-central-1.amazonaws.com). Are there other endpoints as well?
I am using Opsgenie EU account.
Thank you,
Jijin
Hi @jijin_puthuvakkattil - When you setup OEC, and either create an OEC integration, or enable one of our OEC supported integrations (e.g. Jira, JSD, etc.) with "Send via OEC" enabled - it creates a queue in Amazon SQS where the Opsgenie alert data will be pushed to. And then when you paste in the API key into the OEC config file and start OEC, OEC is then subscribed to that queue.
So the sqs domain should be the only url that OEC will need to access. Hope that helps!
Thanks,
Samir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.