api {
    web_server: 

    api_server: 

    files_server: 

    credentials {
        access_key: key
        secret_key: secret
    }
}

sdk {
    aws {
        s3 {
            bucket: bucket-name
            key: my-key
            secret: my-secret
            secure: true
            verify: "etc/ssl/certs/ca-certificates.crt"
            multipart: false
        }
    }
}

_reload() prints ('verify', '/etc/ssl/certs/ca-certificates.crt')

U want to share your clearml.conf here?

Originally I wanted to use the environment variable AWS_CA_BUNDLE=/etc/ssl/certs however it seems boto3 doesn't respect that variable from my testing

I not very sure tbh. Just want to see if this is useful....

I got SSL error few days back and I solved it by adding cert to /etc/ssl/certs and perform update-ca-certificates .

export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt

Add this. Note that verify might not work with sdk.aws.s3.verify but sdk.aws.s3.credentials . Pls see the attached image.

Example:
aws {
s3 {
credentials: [
{
# This will apply to all buckets in this host (unless key/value is specifically provided for a given bucket)
host: "<minio hostname>:443"
key: "your key"
secret: "your secret"
multipart: false
secure: true
verify: /etc/ssl/certs/ca-certificates.crt
}
]
}
}

None

hope this helps.

I have, _reload() prints ('verify', '/etc/ssl/certs') while __init__() simply prints {'endpoint_url': ' None ', 'use_ssl': True, 'verify': True, 'region_name:' None, 'config': <botocore.config.Config object at 0x7f4408d08a00>}

https://clear.ml/docs/latest/docs/integrations/storage/
Try add the <path to your cert> for s3.credentials.verify.

the config that gets sent to boto3 still only has verify=True