[Bug]: S3 access issue when using HTTP proxy

[jonnyxux]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: 2.4.10
- Deployment mode(standalone or cluster):standalone
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus
- OS(Ubuntu or CentOS): Amazon Linux 2023
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

When I configure the HTTP proxy to access the S3, there is always some errors to list the S3 bucket, here is the details:

I checked the source code, it looks like the proxy server didn't set in the S3 C++ SDK used by Milvus.

Expected Behavior

The milvus can access S3 with HTTP proxy

Steps To Reproduce

With this config on docker-compose.yml file:
standalone:
    environment:
      ETCD_ENDPOINTS: etcd:2379
      HTTP_PROXY: "${http_proxy_server}"
      HTTPS_PROXY: "${http_proxy_server}"
      NO_PROXY: "169.254.169.254,etcd,localhost,127.0.0.1,172.18.0.3"

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @LoveEachDay
/unassign

[yanliang567]

@jonnyxux I don't think your config is correct, please refer to this one: https://milvus.io/docs/deploy_s3.md#Configure-S3-with-Docker-Compose

/assign @jonnyxux