Configuring CORS for Custom Storage Buckets

  • Updated

To enable seamless access to the objects within your custom storage bucket from the LucidLink Web App, you need to configure a Cross-Origin Resource Sharing (CORS) policy. Without the proper CORS policy, you won't be able to download files by using the web client. The desktop and mobile clients do not require this policy.

This article outlines the required settings to ensure secure and efficient communication between LucidLink and your storage provider.

CORS policy

To enable the LucidLink Web App (https://app.lucidlink.com) to access your storage bucket, configure the following CORS policy in your bucket settings:

  • Allowed Origins: https://app.lucidlink.com

    • Only requests from this origin will be permitted.

  • Allowed Methods: GET, PUT, HEAD

    • The web app can retrieve files, upload files, and check metadata.

  • Allowed Headers: * (All headers allowed)

    • Any request headers can be included.

  • Exposed Headers: None

    • No additional response headers will be accessible beyond standard ones.

Here is the above in json format:

[
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["GET", "PUT", "HEAD"],
"AllowedOrigins": ["https://app.lucidlink.com"],
"ExposeHeaders": []
}
]

How to Apply This Policy

Refer to your storage provider’s documentation to set up the necessary CORS rules, as the format may vary. Ensure that the above settings are correctly applied to allow smooth integration with the LucidLink Web App.

Here are links to the documentation from popular cloud storage providers on this topic:

AWS S3 

Azure 

IBM

Google Cloud

 

If you believe you have applied the correct settings but are still not able to download files from the LucidLink Web App, please contact our support team.

Was this article helpful?

0 out of 0 found this helpful