Can anyone tell me if it is possible to connect QuickSight to the Redshift cluster which is not publicly accessible?

Documentation tells only this:

Q: How do I connect my VPC to Amazon QuickSight?

If your VPC has been set up with public connectivity, 
you can add Amazon QuickSight’s IP address range to your database 
instances’ security group rules to enable traffic flow into your VPC 
and database instances.

Our VPC is publicly accessible, but Redshift attached to private subnets and has "Publicly accessible" - NO. (I think the same question is related to the RDS clusters with private access)


You can connect QuickSight to Redshift running in a private VPC now using the 'Enterprise Edition' of QuickSight.

From the FAQ:

Q: What does private VPC access in the context of Amazon QuickSight mean?

If you have data in AWS (perhaps in Amazon Redshift, Amazon Relational Database Service (RDS), or on EC2) or on-premises in Teradata or SQL Server on servers without public connectivity, this feature is for you. Private VPC (Virtual Private Cloud) Access for QuickSight uses an Elastic Network Interface (ENI) for secure, private communication with data sources in a VPC. It also allows you to use AWS Direct Connect to create a secure, private link with your on-premises resources.


| improve this answer | |

You wanted to know if it is possible to connect Quicksight to a Redshift cluster running in private VPC. Unfortunately, since quicksight resources are running outside the customer VPC, it is not possible to access the redshift cluster which is in private VPC. As per our discussion following document talks more about how to configure the security groups for quicksight to access redshift :


| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.