Syncovery on AWS ECS Fargate - instance sizing
Posted: Fri Jan 12, 2024 2:07 pm
Hello
We are running a Syncovery instance on a Windows server EC2 in AWS which is likely way overkill.
We would like to optimize our costing and move to a docker instance running in ECS Fargate instance but we would need advices on sizing the instance in terms of vCPU, RAM and local storage
Our typical usage includes transferring everyday between 100 to 500 large video files from 1 GB to 50GB (occasionally up to 100GB)
Do you have some guidelines to help us with that ?
When moving files, are the files temporarily stored locally ? so should we account for local storage able to cope with the potentially large video files tat we are transferring ?
Let us know if you have any question to help with that
Best regards
We are running a Syncovery instance on a Windows server EC2 in AWS which is likely way overkill.
We would like to optimize our costing and move to a docker instance running in ECS Fargate instance but we would need advices on sizing the instance in terms of vCPU, RAM and local storage
Our typical usage includes transferring everyday between 100 to 500 large video files from 1 GB to 50GB (occasionally up to 100GB)
Do you have some guidelines to help us with that ?
When moving files, are the files temporarily stored locally ? so should we account for local storage able to cope with the potentially large video files tat we are transferring ?
Let us know if you have any question to help with that
Best regards