By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

QuickSight requires 32 ip addresses to be whitelisted to connect to data source

0

Trying to connect QuickSight to a database in Azure controlled by a vendor. Have sent over the ip range to whitelist for us-west-2.

IP address range for data source connectivity – 54.70.204.128/27

Was told that is too many ips to whitelist. The most they are willing to whitelist is 3 ips.

Has anybody had this issue? Is there a work around? Is it possible to use a dedicated ip address to funnel that ip range to a single dedicated ip address?

Thanks, William

Topics
AnalyticsAWS Well-Architected Framework
Tags
Amazon QuickSightSecurity
Language
English
rePost-User-1305705
asked a year ago355 views
2 Answers
0

You are correct with the ip address range. Perhaps forward them the link https://docs.aws.amazon.com/quicksight/latest/user/regions.html

Maybe explain to the vendor how it works with the details above form aws.

profile picture
EXPERT
Gary Mclean
answered a year ago
  • rePost-User-1305705
    a year ago

    I sent that link. They are still concerned. I think they have to manually add the ips one-by-one to an internal whitelist. They suggested to setup a dedicated ip address to route traffic via. They sent an article to how to do that for SES.

0

Hi.

What database in Azure are you trying to connect to?
You can also connect to Azure VNET via VPC via VPN or similar as another option.

https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html

profile picture
EXPERT
iwasa
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content