Attimis OneBucket With Wasabi

Attimis OneBucket can serve as a front end for Wasabi and other cloud storage providers. It allows you to write data to your OneBucket once, and then replicate it to Wasabi and other clouds. The opportunistic replication feature copies data to Wasabi when reading from other clouds, allowing you to start using Wasabi with your existing data immediately.

Requirements

• Active Wasabi Cloud Storage Account.

• Access to the Wasabi Console as the account root user.

• Wasabi bucket created. Do not enable Versioning or Object Lock (see Creating a Bucket for details on this procedure).

• Access to the Attimis OneBucket console.

Configuring Wasabi

1. Log in to the Wasabi Console as the account root user.

2. Configure a policy for an attimis user (that will be created below) using the following policy. See Creating a Policy for instructions on how to create a policy. Change YOUR_WASABI_BUCKET_NAME to your own Wasabi bucket name. Adjust the Actions to meet your organization’s requirements.

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Action": "s3:ListAllMyBuckets",
         "Resource": "arn:aws:s3:::*"
       },
       {
         "Effect": "Allow",
         "Action": [
           "s3:Get*",
           "s3:List*",
           "s3:Put*",
           "s3:Delete*",
           "s3:AbortMultipartUpload"
         ],
         "Resource": [
           "arn:aws:s3:::YOUR_WASABI_BUCKET_NAME",
           "arn:aws:s3:::YOUR_WASABI_BUCKET_NAME/*"
         ]
       }
     ]
   }

3. Create an attimis user and attach the previously created policy to it. For more information, see Creating a User.

   • Allow programatic-only access, not console access.

   • Do not require Multi-Factor Authentication (MFA).

   • It is not necessary to assign the user to a group.

   • Save the access and secret keys in a secure location.

Configuring OneBucket

1. Log in to the OneBucket console.

   

2. On the Credentials tab, click Add Credentials.

   

3. Select S3 protocol and enable the slider next to Download the credential upon creation.

4. Click Generate to generate an access and secret key pair for OneBucket.

5. Optionally, enter a description.

6. Click Add.

7. Save the downloaded file in a secure location.

   

   You will see your new OneBucket access key on the Credentials screen.

   

8. Click Endpoints.

9. Click Create Endpoint.

   

10. Click S3 protocol and give the endpoint a name (for example, Wasabi).  

11. Enter https://s3.wasabisys.com as the URL and enable Use region.

12. Click Add.

    

13. Click Add Credentials.

    

14. Enter your Wasabi access key and secret key, give a description.

15. Click Add.

    

    Your Wasabi keys will now show up under your Wasabi endpoint.

    

16. Click Policies.

17. Click Create Policy.

    

18. Enter a name for your Attimis bucket and click Next.

    

19. Click Add Peer Bucket.

    

20. Configure the policy.

    • Select Synchronous, Asynchronous, or Cache. Since we are only configuring our Wasabi bucket here, we selected Synchronous. Hover your cursor over each type of bucket for a description.  

    • Enable the slider next to Active.

    • Check the box(es) next to the permissions appropriate for your organization.

    • Select the checkbox next to Turn on the opportunistic replication. When data is read from other buckets in this policy, it will copy the data to your Wasabi bucket.

    • Select your Wasabi endpoint from the drop-down.

    • Scroll down.

      

21. Enter the Wasabi region your Wasabi bucket is located in.  

    This configuration example discusses the use of Wasabi's us-east-2 storage region. Use the region where your Wasabi bucket is located. For a list of regions, see Available Storage Regions.

22. Select your Wasabi access key and Wasabi bucket from each drop-down.

23. Click Apply.

    

24. Click Next.

    

25. Click Next.

    

26. Select the checkbox next to your Attimis access key.

27. Click Create Policy.

    

28. Your OneBucket will now show up on the Policies tab.

    

Testing

We are going to use the AWS CLI to test putting a file into our Wasabi bucket via our Attimis OneBucket. For more information, refer to AWS CLI With Wasabi.

1. Create a profile that contains your Attimis access and secret keys. Enter your Attimis access and secret keys when prompted. Leave the default region blank and keep the default output format of json.  

   aws configure --profile attimis

2. Create a Wasabi profile. Enter your Wasabi access and secret keys when prompted. Enter “us-east-1” as the default region and keep the default output format of “json”.

   aws configure --profile wasabi

3. Create a test file. In this example, we will just create a zero-byte “test.txt” file.

   touch test.txt

4. Upload the file to your Attimis OneBucket. Replace YOUR_ONEBUCKET with the name of your OneBucket.

   aws s3 cp ./test.txt s3://YOUR_ONEBUCKET/test.txt --profile attimis \
   --endpoint-url https://s3.cluster8.onebucket.io

5. Verify you can see the file in your Attimis OneBucket. Replace YOUR_ONEBUCKET with the name of your OneBucket.

   aws s3 ls s3://YOUR_ONEBUCKET/ --profile attimis \
   --endpoint-url https://s3.cluster8.onebucket.io

6. Verify you can see the file in your Wasabi bucket. Use the appropriate endpoint URL for your Wasabi bucket. Replace YOUR_WASABI_BUCKET with the name of your Wasabi bucket.

   This configuration example discusses the use of Wasabi's us-east-2 storage region. To use another Wasabi storage region, use the appropriate URL in Service URLs for Wasabi's Storage Regions.

   aws s3 ls s3://YOUR_WASABI_BUCKET/ --profile wasabi \
   --endpoint-url https://s3.us-east-2.wasabisys.com

7. Below are the commands we issued and their results. We omitted adding the Wasabi profile for brevity. After each ls command, we see the “test.txt” file in the output, confirming it is present.