Skip to main content Skip to complementary content
Close announcements banner

Connecting to Amazon S3 through the AWS internal network

The underlying infrastructure of Qlik Cloud has an added benefit to customers who connect to Amazon S3 for analytics workloads. All data transferred from Amazon S3 buckets in the same region as a Qlik Cloud tenant traverse through the AWS (Amazon Web Services) internal network. This provides an additional level of security and protection for your data in-transit.

Connecting to Amazon S3

Connecting to Amazon S3 for analytics workloads requires an Access Key and a Secret Key from AWS to authenticate your connection. When you use an Amazon S3 connector and the S3 bucket is in the same region as your Qlik Cloud tenant, no additional data connection configuration is required to benefit from this change in Qlik Cloud.


Keep in mind the following limitations that apply when connecting data from Amazon S3 to your Qlik Cloud tenant.

  • AWS limits connections over its internal network between Amazon S3 and AWS services within the same region. Any network connections between an Amazon S3 bucket in one region, and a Qlik Cloud tenant in a different region, will go through the public Internet. This behavior is the same with AWS PrivateLink.

  • Connections that require FIPS compliant support will not work with this capability.

  • The Amazon S3 connectors in Qlik Cloud cannot be used with AWS IAM roles to authenticate connectivity.

  • The Qlik VPC endpoint configuration is subject to change frequently. Therefore, do not configure a bucket policy scoped to IP addresses, VPC sources, or VPC endpoints as you may experience connectivity disruptions. Qlik is not responsible for connectivity errors related to Amazon S3 bucket policy configurations.

Validating the Amazon S3 connection

You can validate the internal network connection between an Amazon S3 bucket and your Qlik Cloud tenant using the following AWS options. In both cases, additional AWS charges may apply.

Logging options for Amazon S3

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!