-
Notifications
You must be signed in to change notification settings - Fork 107
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
S3StorageURL Authorization header is malformed; the region 'auto' is wrong. #983
Comments
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. |
We're taking a look, thank you! |
Hi @Sam-tesouro, I wanted to let you know that we’ve recently added support for AWS S3 URLs. You might want to have a look here:
cdn:
configuration:
s3StorageUrl: 'https://[username]:[password]@your-bucket.s3.amazonaws.com'
s3Region: 'us-east-1' You can find more options here: In these sections, you'll find details on how to pass secret keys, access key IDs, and more. The CDN configuration needs to be applied similarly for the controlplane. Give it a try and see how it works for your setup. Additional release links: |
Hi @Sam-tesouro, we had to ship a small bug fix: https://github.com/wundergraph/cosmo/releases/tag/controlplane%400.105.1 You would need to set you configuration like so:
when updating to this version, let me know how things work for you. Thanks! |
Component(s)
controlplane
Component version
[email protected]
wgc version
[email protected]
controlplane version
[email protected]
router version
N/A
What happened?
Description
Targeting s3 for CDN and ControlPlane with URL format https://ID:SECRET@s3.[REGION].amazonaws.com/[BUCKET-NAME] leads to
"stack":"AuthorizationHeaderMalformed: The authorization header is malformed; the region 'auto' is wrong; expecting '[REGION]'"
Steps to Reproduce
https://github.com/Sam-tesouro/cosmo-controlplane-s3-url-issue/tree/main
Expected Result
Successfully list buckets
Actual Result
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Package Manager: pnpm, npm, yarn, etc
Compiler(if manually compiled): (e.g., "go 14.2")
Router configuration
No response
Router execution config
No response
Log output
No response
Additional context
The s3 client is forcing path style urls which were originally slated for deprecation 4 years ago. https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/
Is there any reason why you aren't supporting Virtual-hosted–style requests?
Regardless I suspect I am just missing the correct incantation for an s3 storage url for Cosmo. After trying many different permutations I am hoping it's simple and I can save others the headache in the future with this issue!
Thank you!
The text was updated successfully, but these errors were encountered: