You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running clearml-helm-chart on our k8s cluster and trying to a submit a job which can access a s3 bucket for storing artifacts. We are providing apiserver pods access to our s3 bucket via apiserver service account, by adding the following annotation to it: eks.amazonaws.com/role-arn: <AWS-ROLE-WITH-BUCKET-ACCESS-POLICY>. On the apiserver pods, i can see the following under the containers.Environment section:
The commands were able to access the S3 bucket and perform read and write operations. However, when i try to log artifacts in the same S3 bucket with the clearml api, i get the following error:
ValueError: Could not get access credentials for'<AWS-BUCKET>' , check configuration file ~/clearml.conf
My clearml.conf is straightforward and looks as follows:
When uploading artifacts the settings should be done on the client side, not the server side. The client (SDK in this case) communicated with S3 independently
Describe the bug
We are running clearml-helm-chart on our k8s cluster and trying to a submit a job which can access a s3 bucket for storing artifacts. We are providing
apiserver
pods access to our s3 bucket via apiserver service account, by adding the following annotation to it:eks.amazonaws.com/role-arn: <AWS-ROLE-WITH-BUCKET-ACCESS-POLICY>
. On theapiserver
pods, i can see the following under the containers.Environment section:As a test, i exec-ed in
apiserver
pod, and ran boto3 commands to access the S3 bucket in python shell:The commands were able to access the S3 bucket and perform read and write operations. However, when i try to log artifacts in the same S3 bucket with the clearml api, i get the following error:
My
clearml.conf
is straightforward and looks as follows:To reproduce
I'm simply trying to
Task.init
withoutput_uri
set as the S3 bucket with the setup configured as described above.Expected behaviour
What is the expected behaviour? What should've happened but didn't?
Environment
Related Discussion
#1017
The text was updated successfully, but these errors were encountered: