[BUG] AmazonS3Bucket Does Not Seem to Handle Spaces Gracefully in Folders and Files

[tcasada]

Type of Connector

Independent Publisher Connector

Name of Connector

AmazonS3Bucket

Describe the bug

When using the PUT object functionality and providing a key containing a folder path or filename with spaces in it we are getting AWS Signature errors. Tried URL Encoding but it didn't seem to make a difference.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

Use the Put Object specifying a file or folder (key) containing a space. The error reported is consistently: SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.

Expected behavior

Expected behavior is that the key can contain spaces and handle the PUT creating a folder and/or file with spaces gracefully.

Environment summary

Tested using Logic Apps.

Additional context

Thanks for this connector it generally works great!

[megel]

@tcasada I have seen before such problems with spaces and fixed it already.

However, I can confirm the issue with the current present connector:

But I see also, that my developed connector that contain a couple of fixes works correctly in my test environment:

I guess, #3731 was merged. It might be possible that this isn't rolled out in all regions yet.