Validating Storage Integrations

After setting up a storage integration between Ango Hub and a supported provider, verifying that the integration is correctly configured before using it in a project will help catch errors before they reach production.

This page explains how to validate your storage integration, either as you create the integration for the first time or after you've already created it.

Validating your Storage Integration during Creation

As you follow the steps outlined in the page detailing how to create a storage integration for each provider (AWS S3, Microsoft Azure, Google Cloud Platform), you will reach a point where, after entering your integration's credentials and clicking on "Next", you will be displayed the following dialog:

This is the validation dialog. If you wish to skip validation altogether, you may click on "Create Storage to finalize the creation of the storage integration.

To instead proceed to validation, please follow the instructions in the Using the Validation Dialog section below.

Validating your Existing Storage Integration

From your Organization page, enter the Storages tab. Click on the three dots to the right of the row representing the storage integration you'd like to validate. The following dialog will appear, mostly filled in:

Complete filling in the dialog and click on "Next". You will see the following dialog:

To proceed with validation, please follow the instructions in the Using the Validation Dialog section below.

Using the Validation Dialog

The validation dialog has three main sections:

• Validate Read Access
• Validate Write Access
• Validate CORS Configuration

Validate Read Access

Validate Read Access will help you check whether Ango Hub can read from the storage. This is necessary in order to import assets, use File Explorer, and anything that has to do with detecting and using existing files in the storage.

To validate read access, copy the URL to a file in your storage. This URL will, for example, look something like this (for AWS S3):

https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/demo-assets/circle.png

Then, paste it in the text field above the Validate Read Access button and click on Validate Read Access. If the storage was configured correctly, you will see a green Access Valid message. If not, you will see an error. Please consult the Possible Errors section for how to troubleshoot any error you might encounter.

Validate Write Access

Validate Write Access will help you check whether Ango Hub can create new files in the connected storage.

To validate write access, write the name of a bucket or container in the storage integration you have just created, then click on Create 'ango-test.txt' in bucket root. Ango Hub will attempt to create a file named ango-test.txt in the bucket's root. If write access for the storage was configured correctly, you will see a green Access Valid message. If not, you will see an error. Please consult the Possible Errors section for how to troubleshoot any error you might encounter.

Validate CORS Configuration

Please successfully validate the storage's read access before validating the CORS configuration.

Failure to do so may result in incorrect error messages being displayed.

Validate CORS Configuration is essential to ensure that imported assets (images, videos, and any other asset type) can be displayed on Ango Hub.

To validate the CORS configuration, copy the URL to a file in your storage. This URL will, for example, look something like this (for AWS S3):

https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/demo-assets/circle.png

Then, paste it in the text field above the Validate CORS Configuration button and click on it.

If the storage was configured correctly, you will see a green message. If not, you will see an error. Please consult the Possible Errors section for how to troubleshoot any error you might encounter.

Possible Errors

Error Message	Cause	Potential Solution
Azure, GCP: Bucket is not in this region AWS S3: Bucket is not in this region, use {correct-region}	The selected region does not match the region of the one obtained from the credentials.	Navigate back to the storage integration configuration dialog and change the selected region.
Azure, GCP: Incorrect region AWS S3: Bucket is not in this region, use {correct-region}	The "region" string provided is invalid.	Navigate back to the storage integration configuration dialog and change the selected region.
Access key ID is incorrect	The provided Access Key ID is not correct. There may be a typo The key might be expired or revoked The secret key & access key pair may not be matching	Navigate back to the storage integration configuration dialog and change the access key to the correct one.
Secret key is probably incorrect	While this is a generic error message, it indicates that the most likely culprit is an incorrect secret key.	Navigate back to the storage integration configuration dialog and change the secret key to the correct one. If the error persists, contact support.
Azure: Authentication failed	The account key provided is incorrect.	Navigate back to the storage integration configuration dialog and change the account key to the correct one.
Object does not exist	The object the URL is pointing to does not exist.	Provide a URL to an object that exists in the storage.
Bucket does not exist Azure: Container not found	The bucket/container provided does not exist.	Provide the name of a bucket/container that exists in the storage.
Bucket name is incorrect	You have provided a bucket name that cannot possibly exist in the storage service you have selected.	Provide the name of a bucket/container that exists in the storage.
Access denied	If this is a read validation, it means that the IAM user for S3 and GCS & the storage account for the Azure is not given the correct read permissions to access the file. If this is a write validation, it means that the IAM user for S3 and GCS & the storage account for the Azure is not given the correct write permissions to write to the bucket.	Navigate to the dashboard of your storage provider and ensure you have given Ango Hub the correct permissions. More info on each individual page: Azure, AWS S3, GCP.
Network error: Address not found	It suggests that we can’t access the object with the given URL because the URL does not exist. The most likely case occurs when the account name is incorrectly typed with Azure. It might also be because of: No internet or DNS issues The domain name is incorrect or does not exist	Ensure your internet connection is working, and ensure the URL has been typed correctly.
No response: Possible networking or endpoint issue	We tried to send the request to the providers servers (to get the object or to write the object), but somehow we didn’t receive any response. Please try again later & make sure the region selection is correct. For Azure check account name as well. Possible causes: The server crashed or is overloaded The request is taking too long, leading to a timeout	Try again later, and ensure the region is correct.
A network error occured. This might be due to a CORS configuration issue	For security limitations it is impossible to tell whether a network error is definitely related to CORS, but this error might suggest it is most likely due to CORS. Occurs when validating CORS. We can’t access the object URL, this may or may not be due to CORS.	Follow the instructions in the documentation page for setting up CORS and try again.
Error in request: [errorMessage]	This is an error on Ango Hub's end.	Contact iMerit support.
Invalid URL	Appears when the URL field does not adhere to the structure of GCP, S3, or Azure. It may be a completely invalid URL (for example linking to an unrelated domain), or the URL may not be valid within the context of these providers. For example a valid GCS URL looks like this: https://storage.cloud.google.com/test-private-assets/drag-and-drop.png If you remove the last two slashes, you remove the bucket name and the key name, the URL becomes invalid: https://storage.cloud.google.com/