Setup LiveKit Egress with an S3 destination AWS credentials we pass to the egress request are STS-derived (per our IAM config the session should be valid for 24 hours; we don’t have visibility into the actual effective TTL of the credentials by the time Egress uses them) What happened A call laste…

Egress does not modify the TTL of the token, so I assume the effective TTL of the credentials was < 80m. It’s not my area of expertise, but others have used assume_role_arn to avoid this kind of issue with long-running sessions. This setting has high-level documentation here: Egress API | LiveKit …

Thanks for the response Darryn, boto_session = boto3.Session() credentials = boto_session.get_credentials() session_token = credentials.token access_key = credentials.access_key secret_key = credentials.secret_key req = api.RoomCompositeEgressRequest( room_name=ctx.r…

@Zaheer_Abbas , I think the root cause is that the session_token you pass is a static snapshot of your pod’s IRSA credentials taken at egress-request time. AWS web-identity (IRSA) sessions default to ~1 hour regardless of the role’s 24h MaxSessionDuration, unless the SDK explicitly requests longer. E…

[image] Zaheer Abbas: For the assume_role_arn solution, can you please help share how we can enable and approach this? We are on Scale plan, our project Id - p_3tqm7ro6kbs You would need to please contact support for this request as follows: [image] Frequently Asked Q…

Thanks - let me check on this and get back. Appreciate the help

@darryncampbell - can you please confirm that we can use both access token method and arn token method for the same account at a given time right? NOT for the same egress request, I am meaning to ask if we can use both access token method for one call and arn token method for a different call. Is th…

Yes, you should be able to use both methods got separate calls, however I want to correct something I said previously. This feature is only available to enterprise customers, not scale - apologies for that error.

LiveKit Egress S3 upload fails with `ExpiredToken` after ~80 min call

Egress / Ingress

darryncampbell (Darryn) May 28, 2026, 9:26am 5

You would need to please contact support for this request as follows:

Topic		Replies	Views
S3 Egress Error — "Start Signal Not Received" Agents egress	6	113	March 31, 2026
Egress upload retry policy Egress / Ingress egress , livekit-cloud	1	63	April 30, 2026
Critical Egress Recording Discrepancies Getting Started livekit-cloud	10	121	June 16, 2026
Egress failed with "Egress Timeout" Egress / Ingress egress , livekit-cloud	14	157	August 12, 2026
Full audio_recording_path from session report + indefinite storage Agents agent-sdk-node-js , livekit-cloud	5	89	August 3, 2026

LiveKit Egress S3 upload fails with `ExpiredToken` after ~80 min call

Related topics