sunng87 opened a new issue, #6346: URL: https://github.com/apache/opendal/issues/6346
### Describe the bug One of our (greptimedb) user is trying to setup DigitalOcean Space bucket via S3, and got error: ``` error sending request for url (http://<ip>/latest/api/token): client error (Connect): tcp connect error: Connection refused (os error 111): Connection refused (os error 111) ``` According to the user, this is because the library tries AWS credentials from the metadata service, fails, and then doesn't fall back to the explicit credentials properly. Let me know if additional information is needed. ### Steps to Reproduce A sample configuration for GreptimeDB is like ```toml # Storage options. [storage] # ... # Storage type. type = "S3" bucket = "bucket_name" root = "/greptimedb" region = "fra1" endpoint = "https://bucket_name.fra1.digitaloceanspaces.com/"; # ... # toggled and tested enable_virtual_host_style = false access_key_id = "*******************" secret_access_key = "**********************" ``` ### Expected Behavior According to the docs, digitalocean space should be supported via s3 connector. ### Additional Context _No response_ ### Are you willing to submit a PR to fix this bug? - [ ] Yes, I would like to submit a PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
