Using S3 Browser with the Content Gateway

The following explains how to configure S3 Browser to work with the S3 protocol personality within the Content Gateway.

Instructions

Please follow these steps:

1. Log into the Content Portal using the following endpoint: http://<IP of Content Portal>:<SCSP Port>/_admin/portal. If you have an SSL offloader (e.g. if you use the Swarm Developer Edition) the endpoint is: https://<IP of Content Portal>/_admin/portal

2. Create a new domain within either the System Tenant or another tenant, using the Add button from the upper right corner.

   Open

   

3. Create a bucket within the newly created domain using the Add button from the upper right corner.

   Open

   

4. Create an S3 token for the newly created domain using the gear icon from the upper right corner of the UI.

5. Make sure to write down the S3 Secret Key and the Token ID

6. Make sure you have a DNS entry pointing the FQDN of the newly created domain to the IP address of the Content Gateway. For testing purposes you can add that entry to the C:\Windows\System32\drivers\etc\hosts file

7. Open S3 Browser and go to Accounts → Add New Account.

• Select “S3 Compatible Storage” as the Account Type

• The REST Endpoint should be <FQDN of newly created domain>:<S3 port configured in /etc/caringo/cloudgateway/gateway.cfg> if you don’t have an SSL offloader in front of the Content Gateway, or <FQDN of newly created domain> if you have an SSL offloader in front of the Content Gateway (e.g. if you use the Swarm Developer Edition)

• Access Key ID should be the Token ID of the S3 token created at Step 5

• Secret Access Key should be the S3 Secret Key of the S3 token created at Step 5

• If you have an SSL offloader configured in front of the Content Gateway, enable “Use secure transfer (SSL/TLS)”

• In the Advanced S3-compatible storage settings make sure you have “Path style” selected as the Addressing model

8. After clicking on Save changes, select the newly created account from the Accounts menu and you should be able to access the S3 bucket:

Related articles