# Installer aws-console avec Homebrew

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

## installation

```sh
sudo av install brew:aws-console
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install aws-console
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:aws-console
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.24.4
- **Résumé source:** Command-line to use AWS CLI credentials to launch the AWS console in a browser
- **Page d'accueil:** <https://github.com/aws-cloudformation/rain>
- **Dépôt:** <https://github.com/aws-cloudformation/rain>
- **Dernière mise à jour:** 2026-07-25T14:18:27-04:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- aws-console (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

aws-console is the Homebrew-packaged entry point for Rain's `console` command, a small AWS-console launcher built into the AWS CloudFormation Rain CLI. It uses the caller's current AWS credentials to generate an AWS Console sign-in URL and open it in a browser, with options for profile, region, service home page, stack selection, logout, and URL-only output.

### Historique du projet

Rain is maintained under the aws-cloudformation GitHub organization as a Go command-line tool for CloudFormation templates and stacks. Its command set covers formatting, packaging, deployment, logging, stack sets, template generation, and a `console` subcommand; the generated Rain documentation identifies `rain console` as the command that logs in to the AWS console.

### Historique d'adoption

As a standalone Homebrew formula, aws-console is a narrow convenience package rather than the main Rain distribution. Homebrew analytics showed 64 installs in 30 days, 283 in 90 days, and 1,339 in 365 days at the time of this batch, consistent with a niche operator workflow rather than a broad AWS CLI replacement.

### Modes d'utilisation

The command is for IAM role sessions, not IAM users. Its documentation says it reads a profile from the AWS CLI configuration file, can target CloudFormation or another AWS service home page, and can print the generated sign-in URL instead of opening a browser.

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

Package nerds care because it is a tiny subcommand exposed as its own Homebrew package: a focused wrapper around AWS federation and browser login, riding on Rain's CloudFormation-oriented release stream.

### Chronologie

- 2026: Rain's generated documentation lists `rain console` as the AWS console login command.
- 2026: Homebrew formula metadata packages aws-console from Rain v1.24.4.

### Related projects

- rain: the parent AWS CloudFormation workflow CLI.
- AWS CLI and AWS SDK shared config files: the profile and credential source used by Rain's console workflow.

### Sources

- <https://aws-cloudformation.github.io/rain/rain_console.html>
- <https://formulae.brew.sh/api/formula/aws-console.json>
- <https://github.com/aws-cloudformation/rain>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


## 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: ~/.aws/config
- Windows: %USERPROFILE%\.aws\config

## Credential files

- Unix: ~/.aws/credentials
- Windows: %USERPROFILE%\.aws\credentials

## Combined YAML source

View the package source record on GitHub. [combined/aws-console.yml](https://github.com/mxcl/pkgdb/blob/main/combined/aws-console.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