Set up a storage integration with MinIO and S3-compatible custom storage services

How to import assets in private buckets on AWS S3 for labeling on Ango Hub

If you are looking for instructions on how to set up a storage integration with an Amazon AWS S3 bucket, please go to this page.

The page you are currently reading is for MinIO and S3-compatible custom storage solutions.

Administrators and project managers can import assets to Ango Hub from S3-compatible storage services.

Once you have created a storage integration by following the steps in this page, you are ready to import files by providing Ango Hub with URLs to files in your private buckets. You may follow the steps in this page to do so: Importing Cloud (Remote) Assets

Configure CORS (Mandatory step)

The CORS header below allows Ango Hub to send a request to your cloud storage, and allows your cloud storage to explicitly allow requests from Hub. This is a necessary step to ensure Hub can connect to your private bucket.

The steps to follow to set up CORS with Ango Hub can be found here. On that page, you may follow the instructions for AWS S3 buckets.

Connect your Cloud Storage by creating an IAM User for Ango Hub

Once you've set up CORS for your bucket, you will need to create a connection between Hub and the bucket itself.

You will need your bucket's Access Key ID and Secret Key. To obtain them, you will need to create an IAM user on your custom storage provider's management dashboard.

Once you have obtained the two strings, go to your organization's page, then click on Storages and Add Storage.

From the dialog that pops up, pick "S3 Compatible" and click on "Next".

Provide your connection with a unique name, the URL of your MinIO or your S3-compatible service, the aforementioned keys, and the region. Click on "Next".

You will be shown a screen asking you if you'd like to validate whether your storage has been successfully connected to Ango Hub. Please follow the instructions on this docs page for information on how to use the validation form. When you are done, click on "Create Storage". You may click on it immediately if you wish to skip validating your storage integration.

Your bucket will be linked to Hub, and it will show up in your list of integrations.

Integrations belong to your organization, not your user.

If you want to be able to access your non-public cloud data in multiple organizations, you will have to integrate Hub with AWS in every one of them.

Preparing and Uploading the JSON for Import

After connecting your bucket, you will need to prepare a JSON file containing each asset’s external ID as well as the asset's full absolute path and, optionally, other information.

Follow the steps outlined in the docs page on Importing Cloud (Remote) Assets.