# Installer okta-awscli avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de okta-awscli pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:okta-awscli
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install okta-awscli
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:okta-awscli
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.5.5
- **Résumé source:** Okta authentication for awscli
- **Page d'accueil:** <https://github.com/okta-awscli/okta-awscli>
- **Dernière mise à jour:** 2026-07-10T11:10:12Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- okta-awscli (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.5.5
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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

- <https://api.github.com/repos/okta-awscli/okta-awscli>
- <https://devforum.okta.com/t/accessing-aws-cli-through-okta/161>
- <https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithSAML.html>
- <https://formulae.brew.sh/formula/okta-awscli>
- <https://github.com/okta-awscli/okta-awscli>
- <https://github.com/okta/okta-aws-cli>
- <https://github.com/oktadev/okta-aws-cli-assume-role>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour okta-awscli. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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