-
Notifications
You must be signed in to change notification settings - Fork 105
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
S3 region issue #33
Comments
Hey thanks for reporting. You can workaround the Oregon problem for now by setting the
In a future release (0.3) this will change to:
As for Frankfurt there seems to be another issue. That data-center is pretty new. Will need to solve that with S3 tech-support. |
Awesome, thanks for the fast response. Definitely looking forward to see what Amazon's support has to say regarding that Frankfurt issue, because the app is for a local (Belgian) printing company who's customers are all local. |
Did you try the irish datacenter? AFAIK that doesn't even have the preflight issue due to the redirect. It used to have it some time ago, but then amazon fixed it. |
i was actually just testing that :).. and that work as well! So I'll go over Ireland for now. |
Did you have to override the domain for Ireland? |
yes I did |
The reason why Frankfurt doesn't work is because slingshot uses AWS Signature Version 2.
So it needs an upgrade for the signing method. I have totally missed the existence of the new signing method in the docs before. |
Updated README.md regarding issue #33 (S3 Region Issue)
First off, awesome work on this plugin.
I did find an issue with getting slingshot to work with an S3 bucket that's not initialized to the default region (i.e. 'US Standard').
To make sure it was just a region issue, I tried following along with the simple example in the README an posting to 3 different S3 buckets, which are all under the same account, and have gotten the same CORS configuration.
First I added the directive server-side, added the AWS key and secret to Meteor.settings, and configured the S3 buckets. Then I used the uploader from the client using the console:
Here are the issues I ran into following along with the example in the README:
console error log:
console error log:
console log:
The text was updated successfully, but these errors were encountered: