-
Notifications
You must be signed in to change notification settings - Fork 184
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
Cannot get generate_presigned_post to work #219
Comments
I am running into a similar issue, and the presigned urls works for me when actually using s3 |
I don't know the first thing about spring, but based on the debug logs and FileStoreController, this request isn't getting mapped to any handler. I tried to use a presigned put, but I can't get that to work with user-defined metadata either with S3Mock or S3. |
Sorry, but S3Mock currently does not implement the generation of presigned URLs. |
Darn, thanks for the information. |
Well, I can do basic presigned put/get requests with S3Mock, should that not be possible? |
You mean, if you add presigned parameters to a URL, you can request that against S3Mock? #125 lists a bug where a HEAD is possible with presigned parameters allowing only a GET request. |
ah, thanks for the clarification. |
AWS SDKs need to be configured with path-style access, CLI with "endpoint", HTTP access works as well. Presigned URIs can be created against S3Mock when enforcing path-style access in the S3Presigner. S3Mock ignores all parameters for presigned URIs and just serves the request. Fixes #219, #125, #1196
AWS SDKs need to be configured with path-style access, CLI with "endpoint", HTTP access works as well. Presigned URIs can be created against S3Mock when enforcing path-style access in the S3Presigner. S3Mock ignores all parameters for presigned URIs and just serves the request. Fixes #219, #125, #1196
AWS SDKs need to be configured with path-style access, CLI with "endpoint", HTTP access works as well. Presigned URIs can be created against S3Mock when enforcing path-style access in the S3Presigner. S3Mock ignores all parameters for presigned URIs and just serves the request. Fixes #219, #125, #1196
AWS SDKs need to be configured with path-style access, CLI with "endpoint", HTTP access works as well. Presigned URIs can be created against S3Mock when enforcing path-style access in the S3Presigner. S3Mock ignores all parameters for presigned URIs and just serves the request. Fixes #219, #125, #1196
I wrote tests for all presigned requests, everything works as expected. |
@chaen |
Hi,
I am running S3Mock in a container. I try uploading a file there using pre-signed URL with
boto3
. In order to do so, I literally copy paste from the official tutorial:https://boto3.amazonaws.com/v1/documentation/api/latest/guide/s3-presigned-urls.html#generating-a-presigned-url-to-upload-a-file
However, this ends up in a http return code
400
The server does not spit any error nor any message at all.
This is the presigned output I get, which seems quite legit:
Any hint on how I could tackle that ?
Thanks for your help, and thanks for this super useful product !! :-)
The text was updated successfully, but these errors were encountered: