Amazon S3 Cloud backup can no longer write files from a backup job even though it was working prior to April 2014
Last Updated: May 11, 2017 11:32AM PDT
If your existing Amazon S3 Cloud backup job in NovaBACKUP Professional, Server or Business Essentials software was working prior to April 2014 then you may need to modify the configuration of your Amazon S3 account via Amazon's AWS website as well as the NovaBACKUP Amazon S3 device that you had in place prior by editing the properties of that Amazon S3 device. Amazon may have had to make a change to their key policy which forces you to re-generate your keys from the Amazon AWS (Amazon Web Services) management page.
If your Amazon S3 backup job error log mentions "Error: e0020023: Unable to establish a connection. - Job processing failure" and looks like the screenshot below then it could be correctable by following the instructions posted below:
The step-by-step instructions on how to do this are posted below.
This is the particular Amazon AWS "Users" configuration page you will need to browse to:
You can follow the example screenshot below to see what the screen would look like and which button to click on after selecting the user.
First you will select the user that you utilize with the selection check box to the left of the name of the user, then go to the Security Credentials tab, highlighted in yellow in the screenshot above, of that user that you selected. Next click the Manage Access Keys button, circled in the screenshot above, on that screen and create a new key set and utilize that new key set in regards to the new Access Key ID: and Secret Access Key entry areas of NovaBACKUP software's Amazon S3 device properties screen. Enter the new Key ID and Secret Access Key that you just generated and then click the Check Credentials button again to verify the properties of the new key are correct matching Amazon's side.
After following the instructions above for managing the access keys in the "Security Credentials" tab you will click on the "Permissions" tab and then follow the instructions shown below and detailed in this next screen shot:
Once you have clicked on the Permissions tab you will click the "Attach User Policy" button highlighted in yellow in the above screenshot you will see the "Manage User Permissions" screen shown below; make sure to choose "Select Policy Template" and then where it mentions "Administrator Access" under "Select Policy Template" click on the "Select" button highlighted in yellow and circled in red in the following screenshot. After clicking the Select button you will be able to apply the administrator access policy which is necessary for our software to backup to the Amazon S3 device:
Wait about one minute and you can go ahead and try out the Amazon S3 backup job again to see if the files can be written to the Amazon S3 device in the NovaBACKUP software.
If after following the instructions above still results in your backup job does not work for you please go ahead and follow the instructions shown below for one additional operation to do on the AWS side:
Then you will have to via the Amazon S3 AWS Management site create a new bucket name, make the bucket name unique and lowercase so that it is something that is not already in place (Amazon will tell you if it is being used site wide if you try to enter one being used) and set the Region to "US West (Oregon)". We have recently identified that if the bucket region choice is set to Canada (Central) or some other non-"US West" choices it may not work to be able to back up to that bucket and when the connection is made to Amazon S3 the backup will fail based on the bucket's Region setting. The latest AWS regions are displayed in list form here.
Then back on the NovaBACKUP software's Amazon S3 device side change the bucket name to match that new one and save the properties out. Now try a new backup to Amazon S3 to see if it can write your files.