Bring-your-own S3 storage integration
Point MeetStream at your own S3 bucket and recordings land there directly. The media stays in your region, under your retention rules and your access controls, from the start.
What this integration gives you
- Recordings and media written directly to your own S3 bucket
- Data stays in your region and your account
- Your retention and access policies apply, not a third-party default
- Encryption in transit and at rest
- Works alongside webhooks so you are notified as media lands
- Backed by SOC 2 Type 2 under audit, ISO 27001, and GDPR compliance
How bring-your-own S3 works
Instead of media sitting in MeetStream storage, you provide an S3 bucket and MeetStream writes recordings and media straight into it. The files land in your account, in the region you choose, so the data residency and lifecycle decisions are yours. Retention, versioning, lifecycle transitions, and access policies are configured on your bucket exactly as you configure any other storage you own.
This matters most when meeting recordings carry sensitive content. Keeping media in your own bucket means it never becomes something you have to retrieve from or trust to an outside store. It is your object, in your account, from the moment it is written.
Security and control
Media is encrypted in transit and at rest. MeetStream operates under SOC 2 Type 2, currently under audit, is ISO 27001 certified, and is GDPR compliant, so the pipeline that produces and delivers your recordings meets recognized controls before the file ever reaches your bucket.
Bring-your-own S3 also composes cleanly with the rest of the platform. A recording ready webhook tells your systems that a new object has arrived, so you can index it, apply access rules, or kick off processing immediately. You keep custody of the media and MeetStream keeps you informed, which is the combination compliance-minded teams tend to want.
- Encryption in transit and at rest
- SOC 2 Type 2 under audit, ISO 27001, GDPR compliant
- Your region, your retention, your access policies
- Recording ready webhook signals when each object lands
How to connect
- Create or choose an S3 bucket in your own AWS account and region.
- Grant MeetStream write access following the setup in the docs at docs.meetstream.ai.
- Configure the bucket in the dashboard at app.meetstream.ai as your storage target.
- Optionally register a webhook to be notified when each recording is written.
$ curl -X POST \
https://api.meetstream.ai/api/v1/bot \
-H "Authorization: Bearer $API_KEY" \
-d '{"url": "zoom.us/j/74648392"}'
Frequently asked questions
Where are my recordings stored?
In your own S3 bucket. MeetStream writes recordings and media directly to the bucket you provide, in your account and region, so the data stays under your control rather than in third-party storage.
Who controls retention and access?
You do. Because the bucket is yours, your retention rules, lifecycle policies, and access controls apply to the media. MeetStream writes the objects, and everything about how they are kept and who can reach them is configured on your side.
Is the media encrypted?
Yes. Media is encrypted in transit and at rest. MeetStream also operates under SOC 2 Type 2, currently under audit, is ISO 27001 certified, and is GDPR compliant, so the capture and delivery pipeline meets recognized security controls.
How do I know when a recording is available?
Pair bring-your-own S3 with webhooks. A recording ready event tells your systems the moment a new object lands in your bucket, so you can index it or start processing without polling for the file.
Connect it in an afternoon
One API to join, record, stream, and transcribe meetings across Zoom, Google Meet, and Microsoft Teams.