Using the ruby aws-sdk gem, presigned post uploads work correctly with AWS S3 proper and fail when attempting on Spaces. So there is some kind of non-interoperability going on.
I setup everything following this guide, https://devcenter.heroku.com/articles/direct-to-s3-image-uploads-in-rails
It’s failing with this error:
<Error> <Code>InvalidArgument</Code> <Message>Missing access key</Message> <BucketName>bucket</BucketName> <RequestId>tx0000000000000000...</RequestId> <HostId>1d183-nyc3a-nyc</HostId> </Error>
Again, the code works with S3, fails with Spaces. Has anyone got this to work?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
Here is a working example using the
aws-sdk-v1gem, which is required until Spaces supports v4 signatures.
Please let me know if DigitalOcean supports the “Policy” and “X-Amz-Signature” headers? (AWS V4) TIA.
This comment has been deleted