Enabling S3 Storage Using Console

IBM Aspera On Demand can use S3 storage for a node transfer user by specifying the storage in the user docroot. Use this user to transfer files to and from your S3 storage. The steps below assume the following:

You have purchased and booted up your Aspera On Demand product.
You have created an S3 bucket.
You have permissions to create IAM roles or change the policies of your IAM.
You know how to SSH as root to your Aspera On Demand instance.

In Console, select a node and edit its transfer user from the Accounts tab.
Expand Docroot, click Override, and paste the S3 docroot for that user using the following syntax:
```
S3://access_id:secret_key@s3.amazonaws.com/my_bucket/my_path
```
Use URL encoding for special characters in your S3 Access ID and secret key. For example, encode a slash character ( / ) by replacing it with %2F and encode a plus character ( + ) by replacing it with %2B.
Click on the Save Changes button.
For more information about setting a user's docroot, see Editing the User or Group on a Node.
Restart the Aspera NodeD service on the node.
SSH into the node and run the following command:
```
# ssh -i identity_file -p 33001 ec2-user@ec2_host_ip
# service asperanoded restart
```

Configure advanced S3 storage settings and test your configuration.

Optional: Enable advanced S3 storage settings.
- Enable Reduced Redundancy Storage (RRS): Append the following to the docroot:
```
?storage-class=REDUCED_REDUNDANCY
```
  For example, enter:
```
S3://access_id:secret_key@s3.amazonaws.com/my_bucket/my_path?storage-class=REDUCED_REDUNDANCY
```
- Enable S3 Server Side Encryption (SSE). Append the following to the docroot:
```
?server-side-encryption=AES256
```
  For example, enter:
```
S3://access_id:secret_key@s3.amazonaws.com/my_bucket/my_path?server-side-encryption=AES256
```
Test your configuration. Perform a test transfer using an Aspera client to the account configured with the S3 docroot. For information on starting a transfer, see Starting a Simple Transfer.