AWS guide describes a private connection between Amazon Quick and internal data
AWS described how to connect Amazon Quick to internal data using AWS PrivateLink. The procedure assumes AWS Direct Connect or AWS Site-to-Site VPN and separates user access from data retrieval. However, a public path remains necessary for 13 APIs.
A guide from AWS describes an architecture for privately connecting Amazon Quick to data sources on a corporate network. It assumes an existing connection using AWS Direct Connect or AWS Site-to-Site VPN between the corporate environment and the VPC. According to AWS, the described solution is intended to enable internal data transfers without passing through the public internet.
The architecture distinguishes between two paths: user access and API calls go through VPC endpoints using AWS PrivateLink, while VPC connections handle data retrieval from internal sources. The web interface and API require separate VPC endpoints in the same region as the Amazon Quick account. The web interface requires a custom DNS A record; the API can use private DNS. Security groups and VPC endpoint policies further restrict access.
Private access has exceptions: 13 APIs for managing action connectors and automated workflows are not supported through the relevant VPC endpoint. Automation using these APIs needs access to the public API endpoint. If calls to Amazon S3, Amazon Redshift and Amazon Athena also need to use a private path, the guide requires planning VPC endpoints for those services as well. Configuration details are available in the source article.
Why it matters
Administrators gain a concrete basis for designing two distinct network paths. Providing private user access alone does not address internal data retrieval; the design must also include VPC connections and any associated data services.
Relevant practical impact
What this means
For a business
When planning network restrictions, companies must account for the fact that automated management of action connectors and workflows may still require public API access. A requirement for fully private operation may therefore limit which automations can be used.
Risks and complianceCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.