MySQL Shell S3 support has been tested against the following S3-compatible storage services:
MySQL Shell supports configuring AWS credentials in environment variables and in configuration files.
Configuration parameters are used in order of precedence:
Option. For example,
s3Profiletakes precedence over the environment variable
AWS_PROFILE, and the default profile in the configuration file.
Environment variable. For example, the environment variable
AWS_SHARED_CREDENTIALS_FILEtakes precedence over the default location of the
DEFAULT environment variable, if it exists. For example, the environment variable
AWS_REGIONand the environment variable
Parameter defined in a configuration file.
AWS default values.
For example, for the AWS region, in order of precedence:
Region defined in the configuration file.
The default value of
AWS credentials are read in the following order of precedence:
Environment variables, if the
s3Profileoption is not defined.
Credentials file, for the specified profile.
credential_process, as defined in the config file. This configuration type contains an external command which retrieves or generates AWS authentication credentials and writes them to
Config file, for the specified profile.
For information on AWS environment variables, see Environment variables to configure the AWS CLI
You can define the following AWS S3-specific environment variables:
AWS_PROFILE: Specifies the name of the profile to use. This can be the name of a profile in a credentials or config file, or the value
defaultto use the default profile. This environment variable overrides the
[default]profile named in the configuration file. You can override this environment variable with the
AWS_SHARED_CREDENTIALS_FILE: The location of the file used to store access keys. Such as
AWS_CONFIG_FILE: The location of the file used to store configuration profiles. Such as
AWS_REGION: Specifies the AWS Region to send the request to. This value overrides the
AWS_DEFAULT_REGIONenvironment variable and the
profiledefined in the configuration file.
AWS_DEFAULT_REGION: Specifies the AWS Region to send the request to. This value is overridden by the
--s3Regionoption and the
AWS_REGIONenvironment variable, if specified.
AWS_ACCESS_KEY_ID: Specifies an AWS access key associated with an IAM user or role.
AWS_SECRET_ACCESS_KEY: Specifies the secret key associated with the access key. This variable overrides the
aws_secret_access_keydefined in the profile.
AWS_SESSION_TOKEN: Specifies the session token value required if you are using temporary security credentials. This variable overrides the
aws_session_tokendefined in the profile.
MySQL Shell requires the following parameters in one or more configuration files:
aws_access_key_id: specifies the access key associated with the user. If not present, an exception is thrown.
aws_secret_access_key: specifies the secret key associated with the access key. If not present, an exception is thrown.
aws_session_token: specifies the session token required if you are using temporary security credentials. If not present, it is not used to authenticate the user.
region: specifies the cloud service region. If not present, the default value of
credential_process:This configuration type contains an external command which retrieves or generates AWS authentication credentials and writes them to
credential_processcan only be defined in the
For more information, see the following:
If you have installed and configured the AWS CLI, MySQL Shell
reads the connection parameters from the default location,
.aws/, automatically. To use an alternate
configuration, do so from the command line, using the relevant
If you are using Oracle Cloud Infrastructure's S3 compatibility API, see Creating a Customer Secret Key for information on creating the credentials required.
By default, the AWS CLI creates two configuration files,
config, which stores parameters such as
region and output format, and
credentials, which stores access keys
and session tokens. It is also possible to place all
configuration parameters in a single file,
config. For more information, see
Configuration and authentication settings . However,
if you have defined access key and secret access keys in
both files, those defined in the
credentials file take precedence.
The following example shows a default pair of AWS CLI configuration files:
aws_access_key_id = AKIA6AV......
aws_secret_access_key = XHRY579I.....
region = us-west-1
output = json
All failed connections to AWS S3 are retried three times, with a 1 second delay between retries.
If a failure occurs 10 minutes after the connection was created, the delay is changed to an exponential back-off strategy:
First delay: 3-6 seconds
Second delay: 18-36 seconds
Third delay: 40-80 seconds