the clearml github, search for a file named cleanup service dot py (or something to that effect)

credentials for the server to do things with s3 will be in /opt/clearml/apiserver.conf.

for future reference: None

thanks!

Hi @<1603198134261911552:profile|ColossalReindeer77> , the clearml server does not support a clearml.conf file (this is only used by clearml clients), and in any case, the server currently does not hold any credentials for use by the WebApp (or SDK). The WebApp manages it's own state, and each user should input their own s3 credentials (the popup you saw)

@<1523701087100473344:profile|SuccessfulKoala55> thanks so much for your reply. I can see now the source of my confusion:

After I finished deploying the server in AWS , the next step in that page is “ configuring ClearML for ClearML server ”.

Then you start reading on that page and it is confusing because the way is written makes it seem like you are creating a clearml.conf for the server.

So perhaps editing that page could make things clearer so other people don’t make the same mistake I made.

For example the title could be “configuring a ClearML client to work with your ClearML server” or “configuring ClearML to connect to your ClearML server”. Similarly, the info panel could be made clear with a comment similar to what you just told me, indicating that a ClearML server does not use clearml.conf . Happy to do the PR in the docs project if you agree.

A related question… how does the server know how to delete artifacts when the project is deleted if it doesn’t have a clearml.conf with the S3 credentials to do so?

Hey @<1593051292383580160:profile|SoreSparrow36> I am trying to test that if I delete a project the S3 storage gets also deleted. But I am not sure this is even a good assumption as I haven’t found anywhere what the expected/default behaviour is. Do you happen to know anything about this? Thanks.

interesting, where can I find more info? total noob here.

Might be under examples

I think you’d have to run the cleanup service. That’s what seems to be what is controlling deletion based on archived status and some other temporal filters