🚧 Coming Soon! 🚧
Please visit HERE for more information
Last modified April 8, 2025

CORS Support

Cross-Origin Resource Sharing, or CORS, is a process that allows web applications from one domain to interact with resources from a different domain.

Example of using CORS

Let’s illustrate CORS with a simple example.

Imagine you have a bucket full of pictures in JetBackup Storage. You also have a website that lets your users browse these pictures. Essentially, your website (let’s say, “mysite.com”) is connected to your JetBackup Storage bucket.

But there’s a catch - web browsers have safety measures. They don’t like it when a website tries to load content from a different domain. In this case, your website “mysite.com” is trying to fetch pictures from JetBackup Storage, which is a different domain.

This is where CORS comes in. By setting up CORS on your JetBackup Storage bucket, you’re telling the browsers, “It’s OK, mysite.com is allowed to access these pictures.” With CORS, the browser will happily display your photos to your users.

Without CORS, your users would be staring at a blank screen instead of admiring your stunning pictures. That’s why CORS is important for connecting your JetBackup Storage with your web application.

Limitations

Currently, the ability to configure Cross-Origin Resource Sharing (CORS) is only available through the AWS Command Line Interface (CLI) utility. Unfortunately, there is no user interface option available for setting up CORS in our platform at this time.

If you need help getting started with the AWS CLI utility or need to familiarize yourself with how to set up CORS configurations using this tool, we recommend checking out the official AWS guide. You’ll find examples of the cors-configuration file here.

CORS Configuration

Setting up CORS involves using the aws command-line interface (CLI) utility and working with a few commands.

Here are the commands you’ll be using:

  • get-bucket-cors: Retrieve the current CORS configuration for your bucket.

  • put-bucket-cors: Apply a new CORS configuration to your bucket.

  • delete-bucket-cors: Remove the existing CORS configuration from your bucket.

Using the CLI for CORS Configuration

We understand that these commands might sound technical. But don’t worry, we’ve got handy CLI examples here.

Remember, setting up CORS correctly helps secure your data and allows for safe interaction between your bucket and other websites. If you run into any issues or need further assistance, feel free to reach out to our support team.