The changes refactor the way federation token ID is used for AWS IAM credentials. Instead of relying on the userID which was previously parsed, the code now uses the userName which is more easily attributable to the IAM user name in the Cloudtrail events list view.
Old:
New:
Why?
In the Cloudtrail console's event history view, the IAM user name will now display in the user name column. Previously, the user id would display (e.g. AIDA.....).
What changed?
Closes #625
The changes refactor the way federation token ID is used for AWS IAM credentials. Instead of relying on the userID which was previously parsed, the code now uses the userName which is more easily attributable to the IAM user name in the Cloudtrail events list view.
Old:
New:
Why?
In the Cloudtrail console's event history view, the IAM user name will now display in the
user name
column. Previously, theuser id
would display (e.g. AIDA.....).How did you test it?
granted credentials add
.assume -c
.Potential risks
Is patch release candidate?
Link to relevant docs PRs