Connect to an Amazon S3 cloud storage

Attach an Amazon S3 bucket

1. Open the New cloud storage connection dialog. The step depends on whether you want to add a new database connection to workspace resources or attach it to a notebook.

   1. On the Home page, select the workspace to which you want to add a cloud storage connection.

   2. From the left-hand menu of the selected workspace, select Data and switch to the Cloud storages tab. This will open the list of all workspace cloud storage connections.

   3. On the Cloud storages tab, click the Add button in the upper right corner.

      

   1. Go to Main menu | Tools | Attached data or click the Attached data icon on the left-hand sidebar.

   2. Click New connection and select New database connection.

      

2. In the New cloud storage connection dialog, select Amazon S3.

   

3. In the New Amazon S3 cloud storage connection dialog, fill in the following fields:

   • Display name: to specify the name for this data source in your system

   • AWS access key and AWS secret access key: to access your AWS account (details here)

   • Region: to specify your AWS region

   • Amazon Bucket name: to specify the name of the bucket you want to mount

   • Custom options: to specify additional parameters. See the example below

   • Endpoint URL: to specify the website of the bucket you want to mount

   

4. (Optional) Click Test connection to make sure the provided parameters are correct.

5. Click Create data source to finish the procedure.

Configure optional parameters for Amazon S3 data sources

Use the Custom_options field for optional parameters when creating an Amazon S3 data source. Below are two examples of how it can be used.

• To enable SSE-C for S3 data sources, specify the following in the Custom_options: In the Custom_options field, specify the following:

  use_sse=c:/path/to/keys/file

  where:

  /path/to/keys/file is the file that contain keys. Make sure permissions are 600.

• (For Datalore Enterprise only) To provide access based on a role associated with that of an EC2 instance profile, add public_bucket=0,iam_role into the Custom_options field.