Thanks — regarding the recommended auth scheme for sending egress to Google Cloud Storage (GCS): We do not have a GCS-specific egress auth example, but you can use standard Google Cloud authentication used across LiveKit integrations: • Preferred: Service account credentials (JSON key) with least-privilege IAM roles (eg.

roles/storage.objectCreator

or

roles/storage.objectAdmin

) for the target bucket. Provide the key to the egress process via the

GOOGLE_APPLICATION_CREDENTIALS

environment variable pointing to the JSON file, or load the JSON and set the credentials in your egress service at runtime. • Alternative: Application Default Credentials (ADC) if the egress runs on a GCP environment (GCE/GKE/Cloud Run). Ensure the VM/Service Account attached to the instance has the storage IAM roles above. • Security notes: Use a dedicated service account per environment, limit roles to only necessary permissions, and avoid embedding long-lived keys in source code. If possible, rotate keys and store them in a secrets manager. To give exact setup steps for LiveKit egress into GCS, could you tell me: 1. Where the egress will run (your own server, GCE/GKE/Cloud Run, or LiveKit-managed environment)? 2. Whether you prefer using a JSON key file or ADC/instance service account? I’ll provide the concrete configuration and sample request once I know your environment. Sources: Google Cloud STT plugin guide | LiveKit docs | Google Cloud TTS integration guide | LiveKit docs | Gemini Live API plugin | LiveKit docs | Universal Egress