How to set up Cloudimage using Google Cloud as a storage?

You can configure Storage alias for your Google Cloud storage in the Cloudimage Admin panel.

In the menu Settings -> Storage, you need to click on Connect External Storage:

Then choose Google Cloud:

In the Pop up screen you need to fill in the corresponding values - bucket name and Cloudimage Alias.

Example:

If your Google Cloud bucket is located on address //www.googleapis.com/upload/storage/v1/b/mysamplebucket then:

• • • bucket name = mysamplebucket
    • Cloudimage alias - you may choose whatever name you want, but do not forget to prefix and suffix it with double underscores = __somealias__

In case that your Google Cloud bucket requires authentication, you can add it too.

• You need to generate an Authentication JSON file using the guide in the Google Cloud documentation - https://cloud.google.com/docs/authentication/getting-started

• You will be provided with JSON file to be saved on your computer

• Copy the contents of this file and paste it in the field that appears after pressing "AUTH KEY" in the storage settings

The container path can contain a sub-folder chain. That can make the URL even shorter when you would like to share only files within a specific folder in your container. 
For example - you can create dedicated storage aliases for different environments:
- production
- staging
- testing

You may create additional Storage aliases using the "+" button.

After completion of all required steps, press Save. The configuration takes 1-2 minutes to be deployed to our servers.

Now, if the original image is located on
gs://mysamplebucket/file.jpg ,
you can use the following Cloudimage URL:

https://token.cloudimg.io/v7/__somealias__/file.jpg 

In case that the Cloudimage Domain Whitelisting is enabled, please do not forget that the new Storage alias needs to be whitelisted too:

Please note that all aliases have to be unique for your account - aliases set in the Storage sections cannot be used in the alias section.

If you have any questions or issues, please feel free to contact our Software Engineer and mention the following details:

• • Token
  • Short description of the issue (including URLs, screenshot, short video if available)
  • Steps to reproduce the issue.