# Install okta-awscli with Homebrew Okta authentication for awscli. Version 0.5.5 via Homebrew; verified 2026-07-10. ## Install ```sh sudo av install brew:okta-awscli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install okta-awscli ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:okta-awscli - **Package manager:** Homebrew - **Version:** 0.5.5 - **Source summary:** Okta authentication for awscli - **Homepage:** - **Last updated:** 2026-07-10T11:10:12Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - okta-awscli (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.5.5 ## Project history and usage okta-awscli is a Python command-line bridge between Okta SSO and AWS command-line credentials. It authenticates a user with Okta, obtains a SAML assertion, and exchanges that assertion for temporary AWS STS credentials that can be used by awscli, boto, boto3, and other AWS API tooling. ### Project history The GitHub repository was created on 2017-07-22. Its README positions the project as a successor-style implementation inspired by nimbusscale/okta_aws_login, with the important design difference that okta-awscli uses Okta APIs during authentication rather than scraping and parsing HTML. ### Adoption history The package sits in the long-running niche of enterprise AWS federation helpers. Okta developer forum threads from 2017 and AWS documentation for AssumeRoleWithSAML show the underlying need: organizations wanted AWS CLI access without distributing long-lived IAM user keys, using a corporate identity provider and AWS STS instead. ### How it is used Operators configure Okta and AWS profile details in a local okta-awscli configuration file, then run the executable to populate or refresh AWS credential material. The practical workflow is less about general Okta administration and more about making federated, MFA-backed AWS access feel like normal AWS CLI profile usage. ### Why package nerds care For package nerds, okta-awscli is a good example of a small package that encodes an enterprise identity pattern: browser SSO and SAML federation collapsed into a repeatable CLI credential flow. Its continued Homebrew packaging also records the era before vendor-provided AWS federation CLIs fully absorbed this use case. ### Timeline - 2017-07-22: The okta-awscli/okta-awscli repository was created on GitHub. - 2018-2024: Public issues and packaging activity show maintenance around Okta MFA behavior, Python dependencies, macOS certificate handling, and AWS credential edge cases. - 2026-07-01: GitHub repository metadata reported 314 stars, 144 forks, Python as the primary language, and Apache-2.0 licensing. ### Related projects - Related tools include nimbusscale/okta_aws_login, Okta's community-supported okta-aws-cli-assume-role, and Okta's separate okta-aws-cli project. AWS STS AssumeRoleWithSAML is the underlying AWS operation that makes the pattern possible. ### Sources - - - - - - - ## Security Notes No matching local secret-handling manifest was found for okta-awscli. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.okta-aws ## Credential files - Unix: ~/.aws/credentials, ~/.okta-credentials.cache ## Combined YAML source View the package source record on GitHub. [combined/okta-awscli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/okta-awscli.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph