You do not have to use AWS for egress uploads—LiveKit supports any S3-compatible storage provider, including Supabase. To use Supabase or another S3-compatible service, make sure your configuration includes: • access_key: Your Supabase S3 access key • secret: Your Supabase S3 secret key • bucket: The bucket name • endpoint: The S3-compatible endpoint provided by Supabase (must start with

https://

) • force_path_style: Set to

true

Example configuration:

storage:
  s3:
    access_key: your-access-key
    secret: your-secret-key
    endpoint: your-supabase-s3-endpoint
    bucket: your-bucket-name
    force_path_style: true

The error you are seeing (

InvalidAccessKeyId

) indicates that the access key or secret is incorrect, or not recognized by the endpoint. Double-check that you are using the correct credentials provided by Supabase and that your endpoint is correct and starts with

https://

. Also, ensure

force_path_style

is set to

true

, as this is required for most S3-compatible providers. If you continue to see errors after verifying these settings, confirm that your Supabase project supports S3-compatible API access and that the credentials have the necessary permissions. Sources: README.md | Egress output types | LiveKit Docs