https://livekit.io logo
Join Slack
Powered by
Does LiveKit Cloud's managed egress service suppor...
# ask-ai
c
Does LiveKit Cloud's managed egress service support custom S3-compatible endpoints, or is it restricted to native AWS S3?
✅ 1
t
Thanks for reaching out, liberivs. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — you're asking whether LiveKit Cloud's managed egress can write to custom S3-compatible endpoints or is limited to AWS S3. LiveKit Cloud's managed egress supports writing to S3 using an AWS Assume Role flow (you provide an 
assume_role_arn
and 
assume_role_external_id
instead of access keys). That flow is enterprise-only and is designed to upload directly to S3 buckets via temporary AWS credentials. Support for arbitrary S3-compatible endpoints (MinIO, DigitalOcean Spaces, Wasabi, self-hosted S3 APIs, or using custom endpoints without the AWS Assume Role) is not confirmed. In other words: native AWS S3 via role assumption is supported; generic S3-compatible endpoints are not guaranteed to be supported. If you need egress to a specific non-AWS provider, tell me which provider and how you plan to authenticate (IAM role, static keys, custom endpoint) and I’ll help explore possible workarounds or next steps. , with interactive elements
c
is it possible to use cloudflare r2?
t
Thanks — you're asking if LiveKit Cloud's managed egress can write directly to Cloudflare R2. LiveKit Cloud's managed egress supports native AWS S3 via an AWS Assume Role flow (enterprise-only): you provide 
assume_role_arn
and 
assume_role_external_id
and LiveKit uses temporary AWS credentials to upload to an S3 bucket. Cloudflare R2 is an S3-compatible provider, but support for arbitrary S3-compatible endpoints (including R2) is not confirmed. In short: AWS S3 via role assumption is supported; direct R2 support is not guaranteed. If you want, tell me: • whether you’re on the Enterprise plan, and • how you would authenticate to R2 (static access keys, STS-like role, or custom endpoint) With that I can suggest possible workarounds (for example proxying uploads or using your own egress host) and the next steps. , with interactive elements
3 Views
Open in Slack
PreviousNext
Powered by