-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Endpoint isn't used in presigned post #1012
Comments
How are you trying to do this with the |
@hakunin You should be able to simply Ignore the presigned-post |
I am using Since the idea is to use Btw I am using version 2. |
Experiencing a potentially related issue with the ruby aws-sdk (v2) whereby we're using a Ceph endpoint rather than S3 itself (ala similar setup to fake-s3) and when we include 'endpoint' in our config (alongside force_path_style), the gem always returns an error: Aws::S3::Errors::InvalidArgument |
@andretanguy Could you please open a separate issue for that? That looks like a possible separate bug. |
Apply :endpoint option to Bucket#presigned_post Related to #1012
@hakunin - I just merged pull request #1020 which plumbs endpoints through presigned posts created via S3 Objects as well as S3 Buckets within the resource interface. If you're using our S3 resource abstraction, this should be all you need. If you're creating presigned post object directly, you should use the Going to close this now, feel free to reach out if this isn't clear or doesn't fully cover what you need to do. @andretanguy I'd still like to dive in to what you're seeing as a separate issue. |
Thanks alex! |
Hi,
I am using the
fake-s3
gem and it advises to useendpoint
config to pointaws-sdk-ruby
to localhost.What I found though is that the presigned post class isn't aware of endpoints and seems to always return s3 url no matter what.
The text was updated successfully, but these errors were encountered: