is offering two storage options which can be used for keeping your digital files. One of them is Amazon Simple Storage Service (Amazon S3).

Amazon S3 is a storage service that offers industry-leading scalability, data availability, security, and performance.

If your team is using AWS for storing the content, you can connect it to for further file management. As well as with Google Drive, doesn't limit you on the file number and size. In case you need more space, you can always upgrade on the Amazon side.

NB! Currently, integration with Amazon S3 storage is working in beta version. We're still in the process of fixing small bugs and improving the functionality. If you come across any issues, please contact us at and we will be happy to help.

Selecting storage in

How do integration and synchronization work?

As well as with Google Drive, is using Amazon S3 for storing your digital files and doesn't charge for the storage. If you need more space, you can always upgrade your billing plan on AWS side. There is a total synchronization between and your S3 bucket. If you upload or update any content in your library, the changes are automatically saved back to your Amazon S3 bucket.

In case you're using UI to upload your assets, no extra actions are needed. However, if you need to manage files directly from the S3 bucket, it's necessary to synchronize the changes manually. Currently, autosync is not available for Amazon S3 users, so you need to perform manual sync to see the updates in your library. Learn how to make manual sync in

Unlike with Google Drive, thumbnails for all supported file formats are generated by system and are actually stored in your S3 bucket.

You may also refer to our simple instructions on how to use Amazon S3.

How to start using Amazon S3 as storage in

That’s easy. When registering at you need to do the following steps:

  • select Amazon on the storage screen;
  • provide your S3 credentials (AWS access key ID and AWS secret access key);

NB! Please make sure that the provided credentials have the following essential permissions:

  • AmazonS3FullAccess — requires to access and manage S3 storage
  • AmazonSQSFullAccess — requires to enable S3 storage synchronization

Connecting Amazon S3 storage
  • click on the ‘Connect’ button;
  • choose the existing bucket you want to connect to or allow to create a new one;
  • if you choose the existing bucket, wait till the data is synchronized to;
  • click on the ‘Finish’ button.

Once done, you may proceed with uploading files to your library directly.

How to configure the integration with on the Amazon side?

For the integration between your library and Amazon S3 to work smoothly and correctly, it's necessary to configure the corresponding permissions to the bucket. You may always refer to Amazon S3 documentation for more details. Besides, when creating a new bucket, we recommend choosing the region which is the closest to your current location.

New bucket

When creating a new bucket on the third step ‘Set permissions’, make sure that the following checkboxes are enabled:

  1. ‘Block public access to buckets and objects granted through new public bucket or access point policies’
  2. ‘Block public and cross-account access to buckets and objects through any public bucket or access point policies’

Before doing so you need to enable the checkbox at the top ‘I acknowledge that the current settings may result in this bucket and the objects within becoming public’.

Create new bucket

On the ‘Review’ tab double-check that the necessary permissions are enabled and click on the ‘Create bucket’ button.

Permissions in AWS S3 buckets

Existing bucket

To check and change the permissions for the existing S3 bucket, please do the following:

  • Open the bucket settings;
  • Go to the ‘Permissions’ tab;
  • Make sure that the last two points are set to ON;
  • If they are not, click on the ‘Edit’ button in the top right corner to make the corresponding changes described above.
Create new AWS S3 bucket.

For the integration to work properly, you need to make sure that the following permissions are enabled on Amazon S3 side. Please follow these steps:

  • Open the AWS management console
Open the AWS management console
  • Locate the IAM in the Security, Identity, & Compliance column
Locate the IAM in the Security, Identity, & Compliance column
  • Select Policies on the left side
Select S3 AWS Policies

  • Create a New Policy
New AWS S3 Policy
  • Type in the search box “SQS”
  • Expand these actions: Read, Write, and Resources.
  • In the Read section select GetQueueAttributes, GetQueueUrl, ReceiveMessage.
  • In the Write section select CreateQueue, DeleteMessage, SetQueueAttributes.
  • In the Resources section select All.
Actions in the AWS S3
  • In the Resources section select All.
Resources section S3 AWS
  • Press Next in the next "Add tags" window and continue to the Final Window.
Add tags to S3 AWS
  • Press the button “Create Policy” and you are done. Congrats!

Once again, all the required SQS permissions must be enabled for the correct working.

Remember that while sharing assets via a website customized with your company domain name as a web address, it's required to add this custom domain to the CORS configuration of your bucket.

Are there any limitations for Amazon S3 storage?

There are some restrictions on the Amazon S3 side which are to be applied to some features in Here is the list of these restrictions:

  • There is no automatic synchronization from your S3 bucket to, only manual one is available.
  • Assets with the identical file name cannot be located in the same collection.
  • The full path to a file (e.g. ‘MyTeamLibrary/collection/subcollection/filename.jpg’) is limited to 1024 symbols.
  • File/collection name may contain all letters, numbers (0-9), symbols ( _ ( ) ! ? ' & , . * ' )
  • Symbols [] {} “” ‘’ /|\ cannot be used in file/collection name.
  • Max number of symbols in .docx, .doc, .pdf, .txt files is limited to 16 millions.
  • Some file formats are currently not supported.

NB! Most of the above-mentioned limitations will be eliminated in the next releases.

How can I change the current storage option?

We strongly recommend choosing the storage workspace before starting to work with DAM platform. So that you won’t have to migrate from one storage to another. In case you decide to change your current storage type (migrate from Google Drive to Amazon S3 or vice versa), please contact us at and we will be happy to help.

NB! Our Dev Team will be able to assist you only with migrating the data related to the assets. All the files transfer between storages should be made on your side.

Did this answer your question?