Storage
How Flo connects to your storage
Flo works on top of your existing storage. You keep control of media and archives while Flo orchestrates processing, metadata, and delivery.
Storage model
Flo connects to customer-owned storage through:
- S3-compatible APIs for cloud object storage (Amazon S3 today)
- OAuth SaaS connectors for Google Drive
- Enterprise storage connectors for on-premises systems (contact support for availability)
You do not need to migrate content into vendor-managed buckets. Flo ingests and processes media in place, writes back metadata and derivatives, and routes content to production, playout, VOD, and delivery endpoints.
Deployment model
The most common setup is hybrid:
| Component | Where it runs |
|---|---|
| Flo application | Vendor-hosted SaaS on Flomenco infrastructure |
| Your media | Your storage (S3 bucket, Google Drive, etc.) |
This keeps media under your control while giving you full platform capabilities.
What Flo does after connection
Once a connector is active, Flo can:
- Ingest new files automatically (S3 EventBridge events or scheduled polling for OAuth sources)
- Process media: proxies, thumbnails, transcription, AI metadata
- Index assets for search
- Route content through workflows to delivery endpoints
Ingested assets behave like manual uploads: same metadata extraction, search, and pipeline treatment.
Connector types
| Type | Best for | Auth |
|---|---|---|
| Amazon S3 | Enterprise archives, broadcast libraries, customer AWS accounts | Cross-account IAM role (recommended) |
| Google Drive | Team folders, marketing assets | OAuth 2.0 |
One connector per S3 bucket is the standard pattern. Add one or more prefixes on that connector to limit monitoring, or leave prefixes empty for the whole bucket.
Who can configure connectors
Org admins configure connectors under Settings → Connectors. Content managers consume ingested assets in Assets; connector setup requires admin permissions.
How to use
- Sign in as an org admin.
- Go to Settings → Connectors.
- Choose Add Connector and select your storage type.
- Follow the setup guide for your connector:
- Verify the connector card shows Active (green).
- Open Assets and confirm ingested files appear.
Troubleshooting
- Connector stuck in pending. For S3 IAM role connectors, deploy the CloudFormation template in your AWS account and paste the Role ARN. See Connect Amazon S3.
- No assets appearing. Run Test connection on the connector card. For Google Drive, try Sync for an initial backfill.
- Permission errors. Re-check IAM role trust, external ID, bucket policy, or OAuth folder scope.
- Platform errors with no clear permission cause. Contact contact@flomenco.com.