VIDIZMO integration brief · Amazon S3 · vidizmo.ai/integrations/catalog/amazon-s3

Integrations / Amazon S3

Amazon S3

Amazon S3 as the content store, and as a source and destination. Visit website

S3 is the object storage most cloud estates are built on.

It serves as the platform's own content store when a deployment is on AWS, and as a source and export destination for material an organisation already keeps there.

Your Own S3 Account, Now a Governed Library

Open as a two-page brief

Amazon S3 is the object storage most cloud estates are built on, and it often already holds years of recordings and documents nobody has indexed. Nexus uses S3 in three roles: as the content store a portal writes to, as a source it pulls from on a schedule, and as a destination it exports to. The bucket stays in your AWS account, and other applications keep using it.

Amazon S3 recordings, files and folders where they already live connector, on a schedule or as content arrives Nexus library: transcribe, index, search; retention, audited access, chain of custody ask questions across it, run workflows AI Intelligence Hub ask, summarize, cite no-code workflows redact before anything is released Redactor faces, voices, PII in video, audio, images, documents Amazon S3 VIDIZMO

How it connects

As a storage provider, S3 is chosen per portal when a deployment runs on AWS. Private buckets are supported and a customer's own storage account is usable, so the library sits in a bucket you own. Nexus writes new content there and reads it back for playback. Users see the library, never the bucket.

As an ingestion connector, a bucket the organization already fills is pulled on a schedule. Files and their metadata come inbound, scoped by an extension allowlist and excluded folders, with the source hierarchy preserved or flattened. After each file lands, the source object is left in place, moved or deleted, as configured. Ingestion runs on the connector's schedule rather than on S3 events.

As an export connector, content leaves the library for a bucket you name. Export is driven by a stored query, including backfill of existing content, and recreates the folder structure recursively at the destination. Every export is logged. Nothing else flows. Bucket policies, IAM and lifecycle rules stay in AWS, and who can open an item in the library is decided by the portal's roles, not by S3 permissions.

What you can do together

  • Run the portal on a private bucket in your own AWS account, so the library never leaves storage you control, through Nexus.
  • Pull an existing bucket into the library on a schedule, limited to the folders and file types you choose.
  • Give every file that lands a transcript, a place in search, a SHA-384 integrity hash, a custody record and a retention schedule, with Nexus.
  • Ask AI Intelligence Hub, included in both Digital Evidence Management and Enterprise Video Platform, a question across everything ingested, and get a cited answer limited to what you may see.
  • Export a stored query's results back to a bucket, folder structure recreated and each export logged, for a hand-off to another system.

A scenario

  1. SetupThe administrator sets a private bucket in the office's own AWS account as the portal's storage provider in Nexus. Everything uploaded from now on is written there.
  2. Same afternoonThe administrator adds the legacy bucket as an ingestion connector: video and audio extensions only, the scratch folder excluded, hierarchy preserved, source left in place, run nightly.
  3. Next morningA detective opens the library and finds the recordings in their original folder structure, each with a transcript, a SHA-384 hash recorded at ingest and a custody entry for its arrival. She searches one interview for a street name and plays from that word.
  4. Same weekShe asks AI Intelligence Hub, "Which interviews mention a blue sedan?" and gets a list citing each recording and the moment. Retrieval runs under her identity, so recordings she cannot open are never candidates.
  5. A month laterThe case goes to the prosecutor. A stored query exports the case's items to a bucket the attorney's office reads from, folder structure recreated and the export logged.

What stays where

S3 remains your storage

The account, the bucket, the region and the bucket policy are yours. Nexus writes to it or reads from it as configured; it does not administer it.

Nexus touches only what you scope

Ingestion is limited by the allowlist and excluded folders you set. Export goes to the bucket you name. A source object is moved or deleted only if you chose that.

Nothing is replaced

Other applications keep reading and writing the same bucket. The library is a governed view over it, with its own access model, retention and custody trail.

Processing runs where the portal runs

Transcription, indexing, hashing and the assistant run on the portal's own infrastructure, as SaaS, in your AWS account or on your own servers. The content itself stays in S3.

Products and solutions

Next step

See it on your own Amazon S3 instance. We will show the connection made, the data moving and the output, then size it for your deployment.

Request a demonstration  or write to sales@vidizmo.ai

sales@vidizmo.ai  ·  vidizmo.ai/integrations/catalog/amazon-s3

Not what you need?

We build it

Send us your API documentation and we build, test and maintain the connector, at no development cost to you.

Request this integration

Bring an MCP server

If the system publishes a Model Context Protocol server, AI Intelligence Hub connects to it as a client with configuration alone.

Define a REST endpoint

Describe your endpoint and it becomes a node in an agent workflow, without waiting on our roadmap.

Product names, logos and trademarks shown here are the property of their respective owners. Their use does not imply any affiliation with or endorsement by them.