Slack integration IP restriction issues

[josh_brostoff]

We are doing a ServiceNow/Slack integration and created a scripted REST service that Slack requests from.   However, these requests technically are coming from Slacks servers who use AWS.   Their IP addresses are dynamic and constantly changing.

Because we have IP restrictions on our instance, no matter which IP addresses we whitelist, the integration will stop working when the Slack servers IP addresses change.

For other customers who have similar use cases, how have you approached issues like this?   We would prefer not to remove all IP restrictions to our instance.

[risanchez · Accepted solution]

The recommended approach according to the Slack Success team is to use a reverse proxy in AWS. Your Slack application will then connect via the reverse proxy in AWS and you would only need to white-list the single IP address of your reverse proxy, rather than white-listing a bunch of subnets from AWS.  

If you still want to white-list the entire AWS subnets for a specific region, you can obtain that list from AWS directly here: https://ip-ranges.amazonaws.com/ip-ranges.json 

[Runjay Patel]

Watch this video for Slack integration steps by step configuration. Post message on slack channel via flow designer.

https://www.youtube.com/watch?v=YEGLJLubCCY&t=1s&ab_channel=ServiceNowHelpdesk

Please mark reply as Helpful/Correct, if applicable. Thanks!!