Elijah Zupancic
Elijah Zupancic
@qdzlug Is this issue still relevant?
@IliaGe thank you for the bug report. I do not quite understand the context of the error above. This is my understanding: 1. You are trying to setup the gateway...
The nginx S3 gateway does not use the AWS SDK. It is just an example configuration of nginx and some njs (NGINX Javascript) put together that works to proxy requests...
Thank you for sharing your fix @maliankurh. Would you be able to submit it as a pull request?
This type of "feature" is just configuration of nginx rather than changing the S3 authentication workflow. It would make for a good "example", that could live under the [examples/](/examples) directory....
Thank you for filing an issue. Did you set `PROVIDE_INDEX_PAGE=true` when starting the gateway?
Are you using a Docker image to run? If so, what is the version/hash and where was it downloaded from (Dockerhub or github)?
Can you try again with the latest version: `ghcr.io/nginxinc/nginx-s3-gateway/nginx-oss-s3-gateway:latest-20220815`? Be sure to enable `PROVIDE_INDEX_PAGE=true`.
That error means that the http signature generated does not match the one generated by S3, and thus the authentication against S3 fails. Can you provide more details about your...
I have not tried to use the gateway with KMS managed keys. I see that you set `AWS_SIGS_VERSION=4`, so it shouldn't be using v2 keys. I'm guessing that message is...