Repository navigation
馃悰 Refresh Kinesis client credentials when using task role - #2159
Closed
PrenticeRoosevelt wants to merge 1 commit into
Closed
PrenticeRoosevelt wants to merge 1 commit into
PrenticeRoosevelt wants to merge 1 commit into
Conversation
The Kinesis pipeline built its AWS client once in init/2 and reused it forever. With task role credentials (ECS task role, EKS IRSA, instance profile) the session token expires (1h for IRSA), so every PutRecords failed with "The security token included in the request is expired" until the pipeline restarted, even though aws_credentials had already refreshed the credentials. Rebuild the client from aws_credentials at most once a minute when the sink uses task role. aws_credentials refreshes credentials 5 minutes before expiry, so the client always carries a valid token. Sinks with explicit access keys are unchanged. Refs #2078 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Kinesis pipeline built its AWS client once in init/2 and reused it forever. With task role credentials (ECS task role, EKS IRSA, instance profile) the session token expires (1h for IRSA), so every PutRecords failed with "The security token included in the request is expired" until the pipeline restarted, even though aws_credentials had already refreshed the credentials.
Rebuild the client from aws_credentials at most once a minute when the sink uses task role. aws_credentials refreshes credentials 5 minutes before expiry, so the client always carries a valid token. Sinks with explicit access keys are unchanged.
Refs #2078