cloudy garbage

Proprietary computer software that is unique to a specific cloud computing provider, performs a standard function but with a non-standard interface, and with less capability than has existed for more than a decade in normal software. Cloudy garbage has the effect of providing cloud provider lock-in by forcing users to do something conventional but using the provider's unique tools. For example, the Amazon Web Service (AWS) Command Line Interface (CLI) includes "aws s3 sync" that has a unique interface, only works on AWS, and is less capable than traditional rsync.

Using AWS CLI 2 to perform a sync which requires an upload of 104 files, after hours of execution, it never changed the estimate from ~9 files and "(calculating...)." Am I doing something wrong with the AWS CLI or is this just more cloudy garbage?