- Newest
- Most votes
- Most comments
Received a response from Amazon... they are working on a VPC connections that can be used for this sort of a behavior with Q3 as target. For the timebeing, we can add the following IPs into a security group to allow whatever the resource:
3.234.162.252
35.170.12.166
54.88.16.229
Tested this on my preview dashboard and all is well now.
It is hard for me to believe no one faced this in the three months this has been in preview. Looking at a couple of threads in the forum here, I see they are similar to mine, but I see no responses.
I could download https://ip-ranges.amazonaws.com/ip-ranges.json per the document at: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html
Running the following jq command shows me 4087 entries to work with.
$ jq '.prefixes[]|{ip_prefix,region:"us-east-1"}|.ip_prefix' ip-ranges.json
I wonder if creating a security group with these 4087 entries is good enough to get started with Grafana. Any thoughts?
Is there an update on this feature as of yet? We need it as we don't want to expose our VPC RDS instances on public interfaces.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 4 months ago
Yeah, VPC Endpoint make sense as a solution this problem.