We are using the component to upload files to S3. We have this error when sending a 500MB csv file:
The remote server returned an error: (413) Request Entity Too Large. We are using the Object_Put action.
The file is generated in an async timer.
In the documentation: https://docs.aws.amazon.com/AmazonS3/latest/userguide/upload-objects.html
it is detailed the maximum object sizes: Upload an object in parts by using the AWS SDKs, REST API, or AWS CLI – Using the multipart upload API operation, you can upload a single large object, up to 5 TB in size
Am I missing something?
Hi @Laia Ferrando Ferragud,
Can you check from service centre if the logs are created from the component service action, than I guess put_object action doesn't support Multipart Upload. Maybe you can try calling API directly from AWS. As you mentioned put object on S3 supports file upto 5 TB that's right but here issue might be with the component.
Hi @Bhanu Pratap ,
The error is raised from the wrapper I have where I use this service action. However, I did not specify anywhere that I'm using a multipart upload. How could I check that?
The action from the component doesn't have any config related to it either...
Greetings and thank you,
Yes @Laia Ferrando Ferragud, The configuration are not available in the component service action that's why I would suggest to create custom API in AWS or C# extension logic to be able to upload files with big size as in your case.
Hello @Laia Ferrando Ferragud,
You have a challenge ahead, as the extension available in the Forge does not support multipart uploads, and its implementation requires some knowledge.
If you know C#, you can solve your problem by implementing those methods. If you don't, consider reaching out to someone who does.
You can learn more about the topic here: link
Hello again,
I could advance somewhat with changing the max config of the outsystems module by the shared configuration of the factory app
However, now I'm getting a different message: Array dimensions exceeded supported range. This message is generated not in the component, but when calling the wrapped action that contains it