Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[destination-s3]: invalid s3 bucket path gives cryptic/misleading error message #38338

Open
1 task
jettdc opened this issue May 18, 2024 · 0 comments
Open
1 task

Comments

@jettdc
Copy link

jettdc commented May 18, 2024

Connector Name

destination-s3

Connector Version

0.6.2

What step the error happened?

Configuring a new connector

Relevant information

Trying to create an s3 destination with an invalid bucket path ("/") gives a cryptic warning about request signature.

Screenshot 2024-05-18 at 12 27 23 PM

Screenshot 2024-05-18 at 12 28 32 PM

Fixed by just changing the bucket path.

Screenshot 2024-05-18 at 12 26 50 PM

Screenshot 2024-05-18 at 12 29 21 PM

Maybe this is expected behavior but this took me hours to resolve the issue. Some field validation would be nice.

Also note this is an a s3-api compatible destination, not AWS s3, if that's relevant.

Relevant log output

Configuration check failed
Could not connect to the S3 bucket with the provided configuration. The request signature we calculated does not match the signature you provided. Check your key and signing method. (9a91d2a8-5c0c-4f12-8145-be77efc62e83) (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: 4291e87b1dcbb544; S3 Extended Request ID: 470d27307f4777c3; Proxy: null)

Contribute

  • Yes, I want to contribute
@jettdc jettdc added area/connectors Connector related issues needs-triage type/bug Something isn't working labels May 18, 2024
@jettdc jettdc changed the title [destination-s3]: invalid s3 bucket path gives cryptic error message [destination-s3]: invalid s3 bucket path gives cryptic/misleading error message May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants