Unanswered
Hi,
We’Re Deploying Clearml On The Eks And Have An Issue With Authenticating The Server With The S3 Bucket.
The Connection To S3 Bucket Is Not Working.
Our Current Diagnosis: Clearml Internally Uses Aws_Access_Key_Id And Aws_Secret_Access_Key. But We A
The pod has an annotation with a AWS role which has write access to the s3 bucket.
So assuming the boto environment variables are configured to use the IAM role, it should be transparent, no? (I can't remember what the exact envs are, but google will probably solve it 🙂 _
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN. I was expecting clearml to pick them by default from the environment.
Yes it should, the OS env will always override the configuration file section.
Are you saying it is not working for you?
84 Views
0
Answers
2 years ago
one year ago