Please enable JavaScript to view this site.

SQL Backup Master Help

Navigation: Backups > Backup Job Editor > Destinations

Amazon S3

Scroll Prev Top Next More

SQL Backup Master supports the use of Amazon S3 for database backup purposes.


To use Amazon S3 as a backup destination, you must have an Amazon Web Services account. If you don't already have an Amazon Web Services account, you can visit their website in order to create one.


To create a Amazon S3 backup destination within SQL Backup Master, click the Add toolbar button in the Destinations section of the Database Backup Editor window. When prompted to choose a destination, select Amazon S3 and click the Select button.


Account Settings


In order to upload database backup files on your behalf, SQL Backup Master requires the following information:


Access and secret keys - These can be found on the "Security Credentials" page of your Amazon Web Services account.

Bucket name - If you haven't already, log into your Amazon AWS account, navigate to the S3 configuration area, and create a bucket for use by your organization.

Authenticate using EC2 IAM role - See help section below for details.

Service URL - If you use a service or device that is fully compatible with the Amazon S3 storage API, you can enter the corresponding service URL here.


Important: SQL Backup Master will not use your Amazon AWS authentication information for any purpose other than those directly required by the application (e.g. uploading, download, listing, and clean up of database backup files). This information is stored (associated with the backup job) in encrypted form, and is never transmitted to any other external party.


EC2 IAM Role Authentication


If you're running SQL Backup Master inside of an Amazon EC2 instance, you have the option of using IAM role authentication (instead of access and secret keys) by checking the Authenticate using EC2 IAM role configuration option.


This feature requires correct configuration of the host EC2 instance and associated IAM role.


To configure your EC2 instance to grant access to an Amazon S3 bucket, use the following Amazon knowledge center guidance:


Important: You should assign the AmazonS3FullAccess permission to your managed IAM policy when using this feature.


Optional Settings


The following optional settings are also available:


Remote dir - By default, SQL Backup Master will upload database backup files into the root of your Amazon S3 bucket. Here, you can specify a directory name (e.g. "SQL Backups" or something similar) to use instead. If the directory doesn't already exist, it will be created. You can also specify multiple sub-directories by separating them with a forward slash (e.g. "Apps/SQL Backups").

Storage class - Specifies the Amazon S3 storage class that should be used for database backup files. The "standard" and "reduced redundancy" storage class options have different redundancy guarantees and associated costs (please see Amazon S3 FAQ for details).

Concurrency - Allows you to control the number of simultaneous upload request threads. A higher concurrency value may result in faster upload times, depending upon various factors (such as available bandwidth, proximity to S3 endpoint, etc.). Use a lower concurrency value when you wish to constrain bandwidth usage.

Encryption - Use this option to apply Amazon S3 server-side AES-256 encryption to the backup file on the server.

Acceleration - Use this option to engage Amazon S3 transfer acceleration feature. Important: Transfer acceleration must be enabled on the target S3 bucket before you can use this feature.

GovCloud account - Check this box if you're uploading database backups to an Amazon GovCloud account.

Emergency destination - When this option is enabled, the associated backup destination will be used only if all other backup destinations fail.




Each time SQL Backup Master successfully uploads a database backup to a destination, it executes a clean-up procedure.


This allows you to automatically remove database backup files that are older than a specified number of days and/or hours.


Important: Cleanup operations for a given destination will only affect the database backup files associated with that destination.