The design assumes an existing AWS Direct Connect or Site-to-Site VPN connection from the corporate environment to a VPC.
The guide separates user-facing traffic from data-fetching traffic. Console, dashboard, API, and Quick Desktop access can use VPC endpoints; Quick reaching into private resources uses VPC connections. AWS describes security groups and VPC endpoint policies as additional controls, with traffic remaining on the AWS backbone rather than traversing the public internet.
The documented paths include Quick Sight queries to on-premises databases, Quick Flows and Quick Automate calls to privately hosted MCP servers or internal APIs, and Quick Agents invoking those same action connectors. For Quick Index, AWS says VPC connections for knowledge-base sources currently support only Amazon Redshift; Confluence, SharePoint, Box, Google Drive, OneDrive, and Amazon S3 cannot use a Quick VPC connection.
The post does not announce a new Amazon Quick feature, state pricing, or establish that this architecture satisfies any particular compliance requirement for a customer.