- Newest
- Most votes
- Most comments
In my bucket setup I "blocked all public access." Is that a problem?
I apologize for the confusion you're experiencing with your S3 backup setup. Let me clarify some points to help you get started with backing up your Western Digital MyCloud NAS to Amazon S3:
-
Access Key: This is not your login name. This refers to the access key ID that is part of your AWS security credentials. You need to create an IAM user in your AWS account and generate an access key for that user. This key is used to authenticate your requests to AWS services.
-
Private Key: This is not your login password. This refers to the secret access key that is paired with your access key ID. When you create an access key for an IAM user, you'll receive both the access key ID and the secret access key. Keep these secure, as anyone with these keys can access your AWS resources.
-
Remote Path: Using your bucket name is correct. The remote path in S3 typically starts with your bucket name, followed by any folder structure you want to use within the bucket.
To set this up correctly:
- Log in to your AWS Management Console
- Open the IAM (Identity and Access Management) console
- Create a new IAM user or use an existing one
- Under the "Security credentials" tab for that user, create a new access key
- You'll receive an access key ID and secret access key - use these in your NAS backup configuration
- Ensure the IAM user has the necessary permissions to write to your S3 bucket
Remember to keep your access keys secure and never share them. If you're having trouble connecting, double-check that you've entered the keys correctly and that your NAS has internet connectivity. Also, ensure that your S3 bucket permissions allow the IAM user to write to the bucket.
If you continue to have issues, you may want to consult the documentation for your specific Western Digital MyCloud NAS model for any particular requirements or steps for S3 backup configuration.
Sources
Backup a NAS directly to S3 DeepArchive (secondary backup) | AWS re:Post
NAS backup to S3 Bucket. Region Issue | AWS re:Post
answered 2 years ago
Thanks, very much. I will give it a go. Rod Michael
Backup failed again. I generated a "root user" access key and a private key and used them in my WD S3 configuration. I used my bucket name as the remote path.
It's best not to use access keys for your root user - a more secure option is access keys for an IAM User.
Thank you for bearing with me. I believe the reason why my backup was failing was that my WD NAS was "check[ing] parity" after replacement of a HDD. It took more than 48-hours to complete that job. Immediately when it completed the parity check, the backup was able to successfully begin.
answered 2 years ago
Relevant content
asked 3 years ago
asked 3 years ago
asked 3 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 4 months ago

Blocking public access is important to do. If you're using access keys to access your bucket then that's authenticated access, not public access, so won't be affected by that setting.