My company operates Redash at EC2.
We restrict the IP addresses that can be accessed by Security Groups.
In the past, just by allowing IP addresses of 184.108.40.206, images of the graph were uploaded by Slack bot.
However, recently the image of the graph has not been uploaded with the IP address of 220.127.116.11 alone.
As I looked it seemed to be accessing with various IP addresses.
Is it possible to fixed the IP address that Slack bot accesses to create graph images?
Yes, we moved the service that creates the snapshots to AWS Lambda and it no longer has a static IP. We might move it into our VPC at some point, which has a static IP address (using NAT gateway), but no ETA for this.
Thank you for your reply.
For security, I would like to allow Redash to access only slack bots, but is there a way to do that?
For now you don’t have any option like this