Add Custom Session Name Using Okta Username #481
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.
This change allows AWS session names to use the Okta username instead of the default
botocore-session
format, enhancing traceability and user identification in AWS logs.By modifying
_get_sts_creds
to accept asession_name
parameter and passing the Okta username assession_name
fromprepare_data
, this update sets the AWS session name to the authenticated Okta username. This is especially useful for environments with multiple users, making it easier to track and identify session ownership across AWS services.