For the file-sync rule itself, there shouldn't be any size limit from a technical point of view (except the maximum file size allowed by the file-system on your server and the amount of available storage space on your cloud server).

From a non-technical point of view,  there may be limit/quota artificially imposed to cover the cost of extra storage space and the amount of out-going traffic for the cloud instance hosted on Amazon AWS.   E.g. if the file-sync rule is configured to unconditionally download (i.e. always overwrite irrespective of file content differences and/or timestamps)  files to devices every 5 minutes, the traffic can add up to massive amount even if file size is a few MB and there are only a few tens of devices.  This amount of outgoing traffic does not pose cost problem for on-premises implementations, but can be significant for cloud server implementations hosted on AWS.  

Thanks Raymond for sharing your insights. Appreciate it.


Anybody here from SOTI to confirm/add on Raymond's statement?