AWS CLI identity federation replaces static credentials with temporary, scoped access tied to a trusted identity provider. Instead of creating IAM users and juggling access keys, you use a federation link from your SSO or enterprise IdP—Okta, Azure AD, Google Workspace, or any OIDC/SAML provider. The AWS CLI starts a session using Security Token Service (STS), giving you time-limited credentials that vanish when they expire.
This changes how teams work. Developers no longer store secrets. Engineers no longer rotate keys. Access is verified in real time against the identity provider, enforcing your org’s policies automatically. Audit logs show who connected, from where, and for how long.
The setup flow is simple but powerful. Configure your AWS IAM Identity Center or federation roles. Map those roles to groups in your IdP. Enable AWS CLI SSO profiles or OIDC-based federation. Test it. No manual credentials. No forgotten key files. From that point forward, running aws s3 ls or aws ec2 describe-instances starts a secure, federated session behind the scenes.