Securing Quick access from corporate networks with AWS PrivateLink
Learn how to connect on-premises data sources to Amazon Quick privately with AWS PrivateLink, keeping analytics traffic off the public internet. This walkthrough covers VPC endpoints for user and API access, VPC connections for data sources, DNS and endpoint policies, identity federation, and enforcing VPC-endpoint-only access for compliance.
First seen by Oriel on .
AI summary
The guide explains how to connect corporate and on-premises systems to Amazon Quick privately using AWS PrivateLink endpoints and Quick VPC connections over Direct Connect or VPN.
- Two interface endpoints handle private user and API access: `com.amazonaws.<region>.quicksight-website` and `com.amazonaws.<region>.quicksight`; the website endpoint also requires private DNS configuration.
- Quick VPC connections place elastic network interfaces in selected VPC subnets so Quick can reach private databases, internal APIs, and on-premises systems reachable through Direct Connect or VPN.
- The website endpoint policy requires `Principal`, `Action`, and `Resource` to be `*`, with conditions limited to `aws:PrincipalAccount` or `aws:OrgId`; API endpoint policies can restrict actions.
- The guide lists 13 action connector and flow APIs unavailable through the API endpoint, and says Quick Index VPC connections currently support only Amazon Redshift among the described private knowledge-base sources.
- VPC connections require Amazon Quick Enterprise edition; setup also depends on supported Regions, appropriate IAM permissions, DNS forwarding, and endpoint security controls.
#aws privatelink #amazon quick #vpc #network security
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| AWS Machine Learning Blog | 34e5ea1686b4ddadf422c6b8da002f20b620869c | https://aws.amazon.com/blogs/machine-learning/securing-quick-access-from-corporate-networks-with-aws-privatelink/ Read discussion |