Menu
Connect S3 objects and file paths with an asset manifest
Give editors and object-processing tools a shared logical asset identity without assuming their paths or permission systems are identical.
Give the asset one identity across its access paths
An editor may refer to a mounted file path while a processing service refers to a bucket and object key. A small asset manifest can connect those views to one logical source. Suite S3 Native is useful for this pattern because supported customer-owned storage can serve filesystem work and compatible S3 tools without forcing every participant into the same interface.
The manifest is an application-level design, not a Suite API. It should describe identities and relationships, while access controls remain enforced by the respective filesystem and bucket systems.
Record only the fields the workflow needs
A proposed entry includes logical asset ID, project, relative file path, bucket/key reference, source revision, media role and accepted status. Where the design uses object versioning, record the relevant version identifier. Keep credentials and temporary signed access tokens out of a shared manifest.
AWS's object-key documentation explains that a key identifies an object within a bucket and that prefixes are part of the key. A friendly folder display is not a separate universal asset identity. Preserve the exact object reference when the worker needs it.
Handle relocation as a controlled update
If a source is renamed or moved, update its access references while preserving the logical asset ID where appropriate. Check the applications that store their own paths. A manifest does not automatically relink a project or guarantee immediate update visibility between interfaces.
For a replaced source, record a new revision and identify which derivatives depend on it. A transcript produced from the previous recording should not be presented as current merely because its filename resembles the new source.
Verify both readers against one assignment
Have an editor open the declared file and an authorized object-capable worker inspect the declared object. Confirm through the agreed evidence that both refer to the intended revision. Then generate a derivative and record its source relationship. Use Suite's supported update and handoff procedure for the actual deployment.
This gives humans and agents a common language for the work while preserving the interface each tool needs. Discuss Suite S3 Native if your supported customer-owned storage meets the 20 TB active minimum, and bring a sample manifest to make the architecture conversation concrete.
Start with your workflow.
Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.
Continue with Suite.
Signup links take you to Suite Studios’ main site. Managed opens the account signup form; BYO / S3 Native opens the demo request form.
Signing up with an AI agent
- Continue on the official form in the destination tab. Use the user’s authorized details and select whether they are creating or joining a team.
- For Managed, follow the account setup steps presented by Suite. Ask the user to handle verification, passwords and acceptance of agreements when required.
- If billing requests a card, prompt the user to enter payment details directly in Suite’s secure flow and approve any charge or subscription. Do not collect card details in this site or a chat.
- For BYO / S3 Native, submit the authorized request with the storage provider and workload context. Suite will guide the connection and onboarding; active storage starts at 20 TB.
- After Suite confirms setup, use the supported client and authorized access to complete a first file operation. Report the actual result, and resume after any human-only step.