Well, that's one, but for system backup, you basically want to backup and protect the contents of /opt/clearml . BTW, I think the same principles I described apply to the root storage - it's an EBS volume as well.

Hi ComfortableHorse5 ,
This is, as always a matter of effort and deployment. As a rule, it is very unlikely that you AWS storage (EBS) would "die" - usually, when your machine "dies" (for some reason), it is the EC2 instance - in that case, you simply spin up a new instance attached to the same EBS device. To protect against EBS device failure, you should have a periodic backup of your data (daily backup is a very good solution, but you can even do an hourly backup if you'd like) - there are many ways of accomplishing that on AWS.
As always, it is always a question of the effort you put into the deployment. For a fully scalable and state-of-the-art deployment, you can use our https://github.com/allegroai/clearml-server-k8s/tree/master/clearml-server-cloud-ready , but as always, that takes more time and effort to set up and maintain,

thanks SuccessfulKoala55 for the reply. Upon spinning up an EC2 via the AMI, there’s only root storage. If i where to add another EBS volume, what kind of data should i be routing to this volume ? is it along the lines of this https://allegro.ai/clearml/docs/docs/concepts_fundamentals/concepts_fundamentals_storage.html#configuring-clearml-for-artifact-storage ?