-
Notifications
You must be signed in to change notification settings - Fork 240
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
How to set s3 region? #82
Comments
You should be able to set this using these variables: Lines 27 to 41 in b9faece
Does that help? |
hmm, i dont see a |
I must admit that I'm not too familiar with S3. Doesn't setting a custom endpoint allow you to set the region as well (URL prefix)? If not, I'll probably be able to take a look into this after the weekend. |
Im not very familiar with that too, looks like there is no standard for s3 url yet other apps like gitlab support s3 region config. If you are using a 3rdparty lib, it might be easy to implement |
I'll be the first to admit my S3 knowledge is severely lacking but I use Send (docker compose) with Minio. The S3 Region I have set in Minio is not the one Send uses by default, but it works. Do you have S3_USE_PATH_STYLE_ENDPOINT set to "true"? I did have to change one section of the IAM policy that @timvisee has on GitLab to:
|
Use can set environment variable |
Having a similar issue, the path style variable however does not solve the issue. |
I think you have make some mistake on your config, I just try a simple setup, its work like a charm
|
Can you confirm, what region do you have your Minio set too? |
@boomam I dont see Minio support region https://min.io/docs/minio/linux/reference/minio-server/minio-server.html#environment-variables Can you post your config and the log of error? Its hard to understand what happened without this. |
Correct, but you still have to specify it on the connection.
I'd have to loop back in a bit to generate the error again, I ended up giving up with Send and deployed something else. Regardless, other than the URL the config for S3 is the same as yours - just not specifying port 9000 being the only difference, as I have all my traffic go through a load balancer on 443/tcp. So the endpoint instead reads as 'https://minio.domain.com'. To be clear on that aspect, it works with other apps - where I can specify the region in use. Your other config examples, such as how you are deploying Minio, are not valid for me as they are on separate systems. |
Had to tidy it up, it dumps it all on one line for some reason in STOUT -
Connectivity between container and service is confirmed, it can get to Minio/S3. |
@boomam From the logs, I think the problem maybe about your config of `
S3_ENDPOINT`
Le ven. 2 juin 2023 à 17:03, boomam ***@***.***> a écrit :
… Had to tidy it up, it dumps it all on one line for some reason in STOUT -
Timestamp=1685717940242000000
Logger=FirefoxSend
Type=send.upload.upload
Severity=2
Pid=1
EnvVersion=2.0
Fields={"error":"UnknownEndpoint: Inaccessible
host: `' at port `443'. This service may not be available in the `us-east-1' region.","stack":"\n
at Request.ENOTFOUND_ERROR (/app/node_modules/aws-sdk/lib/event_listeners.js:611:46)\n
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:106:20)\n
at Request.emit (/app/node_modules/aws-sdk/lib/sequential_executor.js:78:10)\n
at Request.emit (/app/node_modules/aws-sdk/lib/request.js:686:14)\n
at error (/app/node_modules/aws-sdk/lib/event_listeners.js:443:22)\n
at ClientRequest.<anonymous> (/app/node_modules/aws-sdk/lib/http/node.js:99:9)\n
at ClientRequest.emit (node:events:390:28)\n
at ClientRequest.emit (node:domain:475:12)\n
at TLSSocket.socketErrorListener (node:_http_client:447:9)\n at TLSSocket.emit (node:events:390:28)"}
Connectivity between container and service is confirmed, it can get to
Minio/S3.
It's the region its tripping up on.
—
Reply to this email directly, view it on GitHub
<#82 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQ34G6OJGQPMLMXMQVDTQZLXJH6DNANCNFSM5TZ3FNNQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Can you expand on this please, as it looks like your comment may have been cut off? I have also tested other encapsulations, too. Along with specifying and not specifying 443. |
Please try this
|
Already have, noted above. ;-) To re-illiterate in case it was missed, the connection is fine, I can see the connection even in Minio's logs. |
For thoroughness, re-tested regardless -
|
Try check your config of creds, its should not wrap the string in quote |
Same issue. |
lol, gotta laugh - i solved it - regenerating the key to not have special characters. :-p |
I'm using a local minio server with a custom region, while Send is using the default
us-east-1
value. Therefore the s3 authorization header is wrong and denied by minio serverIs there any way to set the region? If not, please add a config.
The text was updated successfully, but these errors were encountered: