macOS
brew install okta-aws-clilocal Homebrew formula metadata
brew
okta-aws-cli のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install okta-aws-clilocal Homebrew formula metadata
nix profile install nixpkgs#okta-aws-clinixpkgs package indexes · pkgs/by-name/ok/okta-aws-cli/package.nix · ソース: api.github.com
概要
Okta federated identity for AWS CLI
履歴
okta-aws-cli is Okta's command-line bridge between Okta identity and AWS CLI credentials. It authenticates through Okta, exchanges identity assertions with AWS STS, and emits temporary IAM credentials for AWS CLI, SDK, process-credential, or credentials-file workflows.
The repository was created on 2022-07-07 as a Go CLI for using Okta as the identity provider for AWS CLI operations. The README describes three primary commands: `web` for human/device authorization, `m2m` for headless machine-to-machine authorization, and `direct` for direct authorization with out-of-band MFA.
The 2.0.0 GA release on 2024-01-25 reorganized the CLI around subcommands, renamed environment variables under the `OKTA_AWSCLI_` prefix, added JSON process-credential output, added an `--exec` mode for running a follow-on command with credentials in the environment, and added support for collecting roles across AWS federation apps.
Subsequent 2.x releases improved multi-profile and multi-app support, non-admin user flows, role and IdP selection, credential formatting, cached-token handling, Chocolatey publishing, and security details such as moving a web SSO token out of the URL query parameter and into a POST body.
The tool addresses a long-standing enterprise operations problem: developers need AWS CLI access through federated identity without long-lived AWS access keys. Okta's own admin documentation tells administrators to get `okta-aws-cli` from GitHub or package managers such as Homebrew or Chocolatey when configuring Okta as the IdP for AWS CLI.
Homebrew usage is comparatively strong in this batch. The formula API generated on 2026-07-01 reported 5,821 installs over 365 days and 5,730 installs-on-request over the same period, reflecting the tool's practical role in developer workstation setup.
In the human `web` flow, a user runs `okta-aws-cli web`, completes browser/device authorization through Okta, and receives AWS `Access Key ID`, `Secret Access Key`, and `Session Token` output. The tool can emit shell environment exports, write or overwrite AWS credentials-file profiles, or return JSON process credentials.
The README explains the SAML-backed path: an Okta OIDC Native Application is paired with an Okta AWS Federation integration app, the AWS federation app is paired with an AWS IAM identity provider, and the CLI presents a SAML assertion to AWS STS with `AssumeRoleWithSAML`. AWS STS returns temporary credentials; AWS documentation says those credentials consist of an access key ID, secret access key, and security token.
For automation, the `m2m` command uses an Okta API service application and private key, then presents an access token to AWS STS using `AssumeRoleWithWebIdentity`. The README warns that private-key handling needs state-of-the-art secrets management and that `m2m` is not intended for human use.
okta-aws-cli is a packaging marker for enterprise identity workflows moving into developer package managers. A Homebrew formula for this tool is not just a convenience CLI; it becomes part of how companies standardize short-lived cloud credentials on laptops.
The package is also a useful metadata case because it wraps several standards and services in one executable: OIDC, SAML, Okta Identity Engine, AWS IAM identity providers, AWS STS, credentials files, environment variables, and process credentials.
セキュリティ状態
narrow executable package without higher-risk signals.
リスク グリーン · 信頼度 低 · appliance
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
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.
Config paths the tool may read or write during local use.
~/.okta/okta.yamlCredential-bearing paths to review before unattended agent runs.
~/.aws/credentials実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
okta-aws-cli | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
https://github.com/okta/okta-aws-cli
インストールメタデータ
| パッケージキー | brew:okta-aws-cli |
|---|---|
| バージョン | 2.6.0 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/okta-aws-cli |
| ホームページ | https://github.com/okta/okta-aws-cli |
| リポジトリ | https://github.com/okta/okta-aws-cli |
| 上流ドキュメント | https://github.com/okta/okta-aws-cli#readme |
| ライセンス | Apache-2.0 |
| ソースアーカイブ | https://github.com/okta/okta-aws-cli/archive/refs/tags/v2.6.0.tar.gz |
| ビルド依存関係 | go |
| Bottle | 利用可能 (対象 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 未定義 |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | okta-aws-cli |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
okta-aws-cli
nix profile install nixpkgs#okta-aws-cliソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.