-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Specific endpoint (S3 OVH) make the boto3 client use the wrong endpoint_url #3258
Comments
Hi @mh4ckt3mh4ckt1c4s thanks for reaching out. Are you sure that you have the correct endpoint configured? Based on this OVH documentation it looks like you might need https://storage.gra.cloud.ovh.net |
Hello @tim-finnigan, thanks for your answer. We tried both endpoints actually, with the same problem. The two endpoints end up at the same location, with |
Have you tried asking in the OVH forums? I would check that you have the correct region configured, and also rule out that any firewall settings aren't preventing the connection. |
Well, you were right, it was the missing I must say that the Anyway, thanks a lot for your help. |
|
Describe the bug
When using
boto3.client
to create a new s3 client, theendpoint_url
specified is sometimes not used properly and partially replaced with an amazonaws URL. Any request then fails as the endpoint is not valid.Expected Behavior
The URL specified in
endpoint_url
is successfully used as the endpoint URL at all times.Current Behavior
The URL was modified by an URL ending with
amazonaws.com
, which is not the domain targeted. Here is the two commands used and the associated logs.Reproduction Steps
Just use these following lines :
And you will see the error with the wrong endpoint URL.
Possible Solution
I think this have something to do with the "s3" part in the URL. Retrying with exactly the same commands but replacing "s3" by "s2" in the URl does not make boto3 use the wrong URL. I rummaged into this repo and the botocore one but without being able to find the code that is actually causing the issue.
Additional Information/Context
We came up with this bug when trying to use the s3 OVH API (https://www.ovhcloud.com/en/) for object storage within a CTFd instance (https://github.com/CTFd/CTFd)
SDK version used
boto3 1.22.7 with s3 v4
Environment details (OS name and version, etc.)
Archlinux with 5.17.2 kernel, but reproduced also in various other environments.
The text was updated successfully, but these errors were encountered: