Cloud Storage Access (Beta)
Cloud Storage Access (Beta)
Cloud Storage Access (Beta)
To ingest assets from your AWS S3 bucket into the Coactive platform, you first need to establish a secure connection that allows Coactive to access your data. There are two supported methods:
Both methods ensure secure, read-only access and are designed to fit different levels of technical complexity and security requirements.
You’ll need:

You’ll now define a policy to allow Coactive to read your dataset.
<bucket-name> with your bucket name.arn:aws:s3:::<bucket-name> refers to the bucket itself — this allows Coactive to perform bucket-level operations such as listing objects (e.g., s3:ListBucket). This is required to view the contents or structure of the bucket during ingestion.arn:aws:s3:::<bucket-name>/* refers specifically to all objects inside the bucket You are also able to specify a prefix here with arn:aws:s3:::<bucket-name>/prefix/* . This grants Coactive permission to read the actual image and video files within that folder (e.g., s3:GetObject).Together, these ensure that Coactive can:
This approach adheres to AWS best practices by limiting access to only the necessary bucket and subfolder.


You’ll now define who can use (assume) this role.
Under “Trusted entity type”, select: AWS account
Under “An AWS account ID”, select Another AWS account and paste:
(This is Coactive’s production AWS account)
Leave “Require external ID” unchecked
Click Next

In the “Add permissions” screen:
Check the box next to that policy to select it
Click Next (bottom-right)

In the “Role name” field, enter a role name:
(Optional) Description:
IAM Role for Coactive to access my personal S3 demo dataset.
Click Create role

The role has now been created!
Now you’ll tell AWS to trust only Coactive’s IAM role.
Click “Update policy”

You’ll need this to register the role with Coactive.
Creat a new Connection using the Role ARN. Please use the API https://docs.coactive.ai/v-1/api-reference/api-reference/connections/create-connection and an example body is:
This approach grants access directly to Coactive’s role via a bucket policy and no IAM role assumption is needed.
Replace all instances of YOUR_BUCKET_NAME with your actual bucket name: