Ok since this issue was never resolved, I am raising something else.
Ok since yesterday my Netdrive app, which has my Amazon Cloud Drive mapped to my local PC, has stopped working. It has worked PERFECTLY for almost a year, and the past 24 hours it has stopped. Folders come and go, items within the folders when I open them are not there, if I restart it they are there. I tried rolling back to various versions of Netdrive, and the problem persists.
You have changed something, and made mounting a network drive unusable. What have you changed and why have you done it, I am very angry right now, I need that data in my ACD and I can't access it the way I want.
I am getting slower S3 upload time, regardless of acceleration and multipart uploads, than upload to an FTP EC2 in the same region. FTP gives about 1Mbps, the S3 is 500 Kbps. Curiously, for our European resources, there's a clear difference between uploads from Windows 7 and Windows 10. Windows 10 S3 uploads are faster than FTP by about 3:1. Windows7 S3 uploads are slower than FTP by about 50%. Again, acceleration and multipart uploads are on. Amazon, please help.
I started a new thread titled "SyncBackPro vs GoodSync for Amazon Cloud Drive", but to make sure it is seen I am also pasting here.
I need to know if anyone has used both SyncBackPro and GoodSync and can say how they compare for Amazon Could Drive. I use SyncBackPro, do not have GoodSync, and am having speed issues. I read the SyncBackPro ACD speed issue thread. I need to verify the upload speed problem I'm having is with Amazon, or whether it's the way SyncBackPro is coded.