To get S3 access working, a few tips that are not well done in the documentation.
The WD app asks for “Access Key” and “Private Key”, but you will see that Amazon will create an Access Key and a Secret Access Key. Simply use the Secret Access Key for the Private Key. Since there is also a private/public key pair option with S3, this can be confusing
Remote Path - it was not clear to me what this is, but it is in fact simply the name of the TOP LEVEL bucket you create (indeed, there is only such a thing as a top-level bucket, within a bucket you can have folders). I was also getting a failure because I was trying to specify a folder like “bucket_name/folder-name”. Only put “bucket_name” in this field
In the S3 dashboard, when logged an on the S3 dashboard, when you are on the “All Buckets” screen, you need to create a top level bucket here, an that is the name you use. You can create a bucket specific for your NAS backup, and then create other buckets for other purposes.
- Using Infrequent-Access Storage option (saves many $$) . Unfortunately, I don’t see any way to set the default for new files uploaded to “infrequent-access” in S3, but do believe the API supports the default setting. However, this would require WD to alter the firmware to support this option. So for now, after your backup completes, select each folder created underneath your bucket (I run several distinct backup jobs, so I have distinct backup folders created under the main bucket) and select PROPERTIES. You can change the folder storage class to “infrequent-access”, and that should change all the files/folders within it to that storage class.