From the source
- It suits enterprises whose data sits behind a corporate firewall or in a private data center, where routing queries over the public internet adds risk and complicates audit trails.
- Amazon says regulatory frameworks such as HIPAA, FedRAMP and PCI-DSS often require sensitive data to stay inside controlled network boundaries.
- The guide assumes AWS Direct Connect or a Site-to-Site VPN already links the on-premises environment to a VPC, then has readers configure VPC endpoints powered by AWS PrivateLink so Quick reaches private resources over the AWS backbone.
- Two mechanisms divide the work: VPC endpoints carry user and API access, while VPC connections, set up in the Quick console, carry data-fetching traffic from databases and internal APIs.
- VPC connections require an Amazon Quick Enterprise subscription, the guide says, and Quick website VPC endpoints are unavailable in the AWS China Regions and AWS GovCloud (US) Regions.
- Amazon also notes that knowledge base VPC connections currently support only Amazon Redshift, while sources such as Confluence, SharePoint and Amazon S3 cannot use one today.
