Amazon S3 Backup Jobs Failing Consistently

We are trying to setup a cloud-based backup onto our Amazon S3 bucket. We have created a test job that connects to the S3 bucket. We tested the account used by the backup job to ensure that the account has the ability to upload files to the destination S3 bucket. The test backup job is a manual backup/copy.

Whenever we attempt to start the backup job, the GUI reports “Backup Failed” after a second or two.

About my NAS:
EX4100 MyCloud
Firmware 2.21.119

Is there anyone having a similar issue?



What region are you using? Try a different region
If you’re using Edge browser, it adds white spaces to the end of the field. Use Chrome or Firefox
Are you sending the backups to /bucket or /bucket/path/path? Try /bucket

Hi, SBrown.
Thanks for the suggestion.
I was using the United States region. Changed to Northern California and Oregon to no avail. Preceeding the bucket remote path with a “/” character produces an error - “The remote path must begin with a-z,A-Z,0-9”

I dug through the file system via SSH and found the /etc/s3.conf file - it indicates that there is an error_code 48 on the backup job.

Usr admin Job InteractBackup dir 0
state 4
error_code 48
count 0
backuptype 0 location 0
AccessesKey zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz (fictitious)
PrivateKey yyyyyyyyyyyyyyyyyyyyyyyyyyyyyy== (fictitious)
BucketPath mprepmediabackup
NASPath /mnt/HD/HD_a2/interact/workspace
Encrypt 0
Schedule Mode=Manual,Date=,Wday=0,Time=0:0

Can you please share with us what your engineers say about error_code 48???


The error code 48 is S3StatusErrorAccessDenied
This normally means the BucketPath does not exists on the server side.

Please check your BucketPath and make sure its all lower case


I’m having the error code 48 problem as well on firmware 2.11.153. I have also checked the Amazon S3 logs and can see that the backup is attempting which suggests to me that the bucket is being properly identified. I’m dieing for a solution to this.

Amazon S3 log

xxxxxx paulzakmycloud [27/Oct/2016:19:26:12 +0000]
xxxxxx xxxxxxx REST.PUT.OBJECT logs/2016-10-27-19-26-12-215F15F—DD486A “PUT /paulzakmycloud/logs/2016-10-27-19-26-12-215F15F—DD486A HTTP/1.1” 200 - - 376 34 11 “-” “aws-internal/3” -

I hope I got all the crypto stuff out!

The system complains with a leading ‘/’ telling us that only numbers and letters are permitted.

One additional thought. The app asks for a 16 character job name which I created.