Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
AkshataIDX
Contributor
Contributor

tS3Put- Your proposed upload exceeds the maximum allowed size

Hi All,

In the latest Talend R2025-10 patch, the AWS SDK was upgraded to version 2.x. After this update, the tS3Put component no longer supports uploading files larger than 5 GB in a single upload. Previously (in R2025-01), the same job worked fine, but now it fails with an error — “Your proposed upload exceeds the maximum allowed size.”
I’ve tried multiple approaches, including multipart configuration, CLI upload, and SDK cleanup, but the issue still persists within Talend. 


Note- It should run in both AWS and studio. 

Thank you,
Akshata.

Labels (5)
4 Replies
Shicong_Hong
Employee
Employee

@AkshataIDX It seems it's Amazon S3 API limitation:

  • Upload an object in a single operation by using the AWS SDKs, REST API, or AWS CLI – With a single PUT operation, you can upload a single object up to 5 GB in size.

For more details, please read in Uploading objects | docs.aws.amazon.com

Can you please double check if it works with Talend Studio R2025-01 when uploading the same file? I will confirm with the R&D team if tS3Put use a different API in these two versions.

Regards

Shicong

AkshataIDX
Contributor
Contributor
Author

@Shicong_Hong 

Thanks for your response. Yes, we’ve verified that the same job deployed using Talend 7.3 runs successfully in AWS without any failure message like “Your proposed upload exceeds the maximum allowed size.”

However, after migrating the job to Talend 8 and deploying it in AWS, we are consistently encountering this maximum allowed size issue when uploading files larger than 5 GB using the tS3Put component.

Kindly confirm with the R&D team if there are any changes in the S3 upload API handling between Talend 7.3 and 8 (especially after the switch to AWS SDK v2).

Thank you
Akshata

Shicong_Hong
Employee
Employee

Thank you for your details, I will get back to you once I have any news from R&D team. 

Regards

Shicong

Shicong_Hong
Employee
Employee

@AkshataIDX I have checked with R&D team and confirmed the issue can be reproduced, it should be considered as a bug and we will fix it. Here is a workaround, hope it is helpful.

To bypass the Transfermanager and utilize multipart-upload, which is suitable for files 5GB and above, you can read the source file as a FileStream on tJava. Subsequently, store the FileStream in a globalMap variable and retrieve it in the "File or stream" field of the tS3Put component.

tJava.pngts3Put.png

Regards

Shicong