You're responding about using

api.S3Upload

and whether you need a dedicated AWS user or can use STS tokens. You can use temporary AWS STS credentials with `api.S3Upload`—no dedicated long‑lived IAM user is required. Provide the STS values in the S3Upload config: • `access_key`: temporary access key • `secret`: temporary secret key • `session_token`: the STS session token This works for all egress types that support S3 uploads (Room Composite, Track Composite, Web, Track Egress, etc.). Using STS tokens is recommended because it avoids long‑term credentials and follows AWS best practices. Would you like an example S3Upload snippet for your egress type? Sources: Egress API | LiveKit docs | RoomComposite Egress | LiveKit Docs | Egress output types | LiveKit docs