Testing Connections to S3

If you can't get the S3 storage engine to work, here are some steps to help verify where the problem could be.

S3 Connection Variables

In most cases the problem is to correctly set the S3 connection variables.

Key are:

• : The AWS access key to access your data

• : The AWS secret key to access your data

• : The AWS bucket where your data should be stored. All MariaDB table data is stored in this bucket.

• : The AWS region where your data should be stored.

There are several ways to ensure you get them right, detailed in the following sections.

Using aria_s3_copy to Test the Connection

is a tool that allows you to copy tables to and from S3. It's useful for testing the connection as it allows you to specify all s3 options on the command line.

Execute the following sql commands to create a trivial sql table:

Now you can use the tool to copy this to S3 from your shell/the command line:

As you can see from the above, is using the current directory as the database name.

You can also set the options in your my.cnf file to avoid some typing.

Using mariadb-test-run to Test the Connection and the S3 Storage Engine

One can use the to run all default S3 test against your S3 storage.

To do that you have to locate the mysql-test directory in your system andcd to it.

The config file for the S3 test system can be found at suite/s3/my.cnf. To enable testing you have to edit this file and add the s3 connection options to the end of the file. It should look something like this after editing:

You must give values for s3-access-key, s3-secret-key and s3-region that reflects your S3 provider. The s3-bucket name is defined by your administrator.

If you are not using Amazon Web Services as your S3 provider you must also specify s3-hostname and possibly changes3-protocol-version to "Original".

Now you can test the configuration:

Note that there may be more tests in your output as we are constantly adding more tests to S3 when needed.

Create a trace of the S3 connection to see what goes wrong

One can use the s3_debug variable to get a trace of the S3 engines interaction with the S3 storage. The trace is sent to the error log.

Here follows one example on can use to get a trace if ALTER TABLE .. ENGINE=S3 fails:

If you have problems deciper the trace, you can always create a ticket on and explain the problem you have, including any errors. Don't forget to include the trace!

What to do when you have got things to work

When you got the connection to work, you should add the options to your global my.cnf file. Now you can start testing S3 from your by converting some existing table to S3 with .

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}