Legacy Qlik Analytics Connectors for Amazon S3 to be deprecated in 2025

[Sonja_Bauernfeind]

Update October 6th, 2025: Added possible migration challenge for ListBuckets.

In an effort to give customers the necessary time to carry out the migration, Qlik has delayed the removal of our legacy S3 connectors. See the updated dates below.

Please proceed with the migration as soon as possible as no further extension will be possible.

The following connectors will be removed and are not recommended for further use:

• Amazon S3 Metadata
• Amazon S3: this is a “File location” connector

Instead, use the following connectors:

• Amazon S3 Metadata V2
• Amazon S3 V2: this is a “File location” connector

The connectors labeled with the suffix “V2” were introduced in 2022 and have since then been the recommended connectors for access to Amazon S3 buckets.

The V2 connectors access Amazon S3 buckets based on the AWS SDK for .NET Core, whereas the legacy S3 connectors were based on the REST API.

The plans to remove the legacy S3 connectors are as follows:

• Qlik Sense Cloud: by the end of August 2025
• Qlik Sense Enterprise on Windows: release November 2025
• Qlik Web Connector (standalone): release June 2025

The legacy S3 connectors and the S3 connectors “V2” have the exact same capabilities, and a migration will in most cases only require a new connection definition and an update in the connection name within the Qlik Script.

The only exception is with the Amazon S3 Metadata connector when the ListBuckets table is used, which may require additional attention. A field name is changed in this table: CreationDate, removing the underscore (_) previously present in the legacy connector (old: Creation_Date).

For this case, the suggestion is to only change the field reference in the initial select statement, but not the alias, so that further references used in the App will continue to work.

Example:

LIB CONNECT TO 'Amazon_S3_Metadata_V2';
[ListBuckets]: 
LOAD CreationDate as [ListBuckets.Creation_Date];
SELECT CreationDate FROM ListBuckets;

 

Additional Reading

• Data sources in Qlik Cloud Analytics 
• Built-in Qlik Web Connectors 
• Qlik Web Connectors 

If you have any questions, do not hesitate to contact us through the Qlik Customer Portal.

Thank you for choosing Qlik,
Qlik Support

[paulcalvet]

Hello @Sonja_Bauernfeind 

Is  the S3 connector for automation concerned by this deprecation ?

There is only one S3 connector for automation.

Regards,

[Sonja_Bauernfeind]

Hello @paulcalvet 

I'll find out for you!

All the best,
Sonja

[Sonja_Bauernfeind]

Hello @paulcalvet 

This is not related to Qlik Application Automation and does not affect it.

All the best,
Sonja

[paulcalvet]

Thank you @Sonja_Bauernfeind ! 

Have a good day !

[Craig789]

Hello,
2 clarifications please.
Does this concern connectors for Talend Data Integration?  There doesn't seem to be any v2 connectors here.

Are all Tenants getting this notification popup or just those Tenants being reported as still using the legacy connectors?  Talend question above aside, I can't find any S3 connectors (I'm new to this role and thus do not have historical knowledge) at all yet we are getting this notificaiton.

Thanking you in advance

[Sonja_Bauernfeind]

Hello @Craig789 

Let me reach out to my experts!

All the best,
Sonja

[Sonja_Bauernfeind]

Hello @Craig789 

This is only related to Qlik Sense (client-managed and Qlik Cloud), meaning there is no concern for Talend Data Integration connectivity. The notification sent to tenants is only intended to be displayed when a legacy S3 connector is still in use. 

All the best,
Sonja

[HawthorneJ_SCFT]

Hi Sonja,

Is there a guide on how to do the migration for Qlik Cloud? I'm not even sure where to look to see the connectors.

Many thanks
Julie

[Sonja_Bauernfeind]

Hello @HawthorneJ_SCFT 

Information on the connectors in Qlik Cloud can be found in Data sources in Qlik Cloud Analytics.

The legacy S3 connectors and the S3 connectors “V2” have the exact same capabilities, and a migration will in most cases only require a new connection definition and an update in the connection name within the Qlik Script.

All the best,
Sonja