S3 Put File Error 500

I am receiving a 500 error when I try to use Put File with S3. The error is:

{status: "500", message: "A header you provided implies functionality that is not implemented",…}
message
: 
"A header you provided implies functionality that is not implemented"
stack
: 
"NotImplemented: A header you provided implies functionality that is not implemented\n    at throwDefaultError (/opt/node_app/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)\n    at /opt/node_app/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5\n    at de_CommandError (/opt/node_app/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4756:14)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async /opt/node_app/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20\n    at async /opt/node_app/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:225:18\n    at async /opt/node_app/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38\n    at async /opt/node_app/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:173:18\n    at async /opt/node_app/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:97:20\n    at async /opt/node_app/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:120:14"
status
: 
"500"

All the actions prior to the Put File work as expected. The file is saved in the local server, renamed, and converted to Webp.

My server action is:

The Put File step is:

Screenshot 2024-04-30 at 6.03.18 PM

I am not quite sure where I have made an error because everything looks ok.

Good Morning,

Any ideas on this issue? I disabled the Put File and everything after it and outputted the Set Values and all the values are working as intended as well.

:frowning:

Sorry to tag you in this @Teodor, but I really am at a loss on this and need some assistance.

If you have a moment, could you look it over for me?

Hi Scott,

It could be an issue with the Path value. I always select Path value from the Save Image step in S3 Put File properties.

2 Likes

Hi @guptast, the Save Image does not have any subs to choose from.

I also have non-image Put Files where Save Image would not be a factor and they are not working as well.

This is what I have in the Save Image properties. Then in the S3 Put File, I bind the value of Path with the name coverItemImage.

Screenshot 2024-05-02 at 3.52.49 PM

1 Like

If I understand correctly, this is what I have done already.

The path in the Save Image selection is:

Screenshot 2024-05-02 at 1.00.02 AM

Which matches the Put File path (with the addition of the image name).

Screenshot 2024-05-02 at 1.00.12 AM

Please try by selecting the Save Image as Path under S3 Put File from the dynamic picker. The error could be originating from S3 API due to no file found or empty data.

2 Likes

Was this your suggestion?

Screenshot 2024-05-02 at 1.33.16 AM

The error remains after making that change.

Just the image_original binding.

2 Likes

Ok, looks like we are making progress. The file uploads, but without an extension.

Well actually, it did sort of. The file uploaded was testpng so it is missing the period separating the name of the file and the file extension, but the file should have been a .webp file.

That’s good. Try these steps for the correct name & extension.

  1. Remove the .webp extension in the set value for upload_id_name.
  2. In the Save Image Template field, change to this value: {{upload_id_name}}.webp
1 Like

Ok, performed those steps and that corrected the missing “.” separating the file name and the extension, but it was still uploaded as a .png.

Screenshot 2024-05-02 at 2.22.00 AM

Screenshot 2024-05-02 at 2.18.42 AM

Screenshot 2024-05-02 at 2.21.20 AM

What’s the file extension in the Template value under File Upload step? Add .webp extension here as well.

2 Likes

Incredible! Thank you so much @guptast!! I do not know if you like coffee like Hyberbytes, but if not, I can send you bagels! :slight_smile:

Thank you so much for your patience in walking me through this. There were many areas where parts were solved, but I think I can only mark one as a solution so I will mark your last post as that.

1 Like

You’re welcome, Scott. I’m glad to know that it’s working as expected.

I enjoy coffee and love to try different types whenever I can :slight_smile: