# awsume を Homebrew, Nix でインストール

awsume のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:awsume
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install awsume
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#awsume
```

  証拠: nixpkgs package indexes: pkgs/by-name/aw/awsume/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:awsume
- **パッケージマネージャ:** Homebrew
- **バージョン:** 4.5.5
- **ソース概要:** Utility for easily assuming AWS IAM roles from the command-line
- **ホームページ:** <https://awsu.me>
- **リポジトリ:** <https://github.com/trek10inc/awsume>
- **最終更新:** 2026-06-22T09:49:41-04:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- autoawsume (エイリアス)
- awsume (エイリアス)
- awsume-autocomplete (エイリアス)
- awsume-configure (エイリアス)
- awsume.bat (エイリアス)
- awsume.fish (エイリアス)
- awsume.ps1 (エイリアス)
- awsumepy (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 4.5.5
## プロジェクトの歴史と使われ方

AWSume is a command-line utility for assuming AWS IAM roles and exporting the resulting credentials into the user's shell environment. It is built around a daily AWS workflow: move between profiles, MFA-backed sessions, and role chains without hand-editing environment variables.

### プロジェクトの歴史

The `trek10inc/awsume` repository was created in March 2016. Its official documentation describes AWSume as a utility for retrieving and exporting AWS credentials from AWS shared config and credentials files, including profiles that require MFA or assume-role calls.

By the v4 era, the docs emphasized shell integration: on Unix-like systems AWSume needs to be sourced or aliased because a child process cannot update a parent shell's environment. The project also grew plugin and extra-feature support, including SAML, fuzzy matching, console helpers, auto-refresh, role chaining, and credential export back into AWS profile files.

### 採用の歴史

AWSume's adoption is mostly among developers and operators managing many AWS accounts or roles. That is a common agency, consulting, and platform-team problem: the standard AWS shared profile format is flexible, but repeatedly calling STS and exporting temporary credentials is tedious.

The official docs recommend pipx or pip rather than Homebrew, while the Homebrew formula still exists for users who prefer system package managers. That split is worth noting: package-manager availability is convenient, but the project itself treats Python packaging as the official install path.

### 使われ方

A normal workflow is `awsume <profile_name>` after shell alias setup. AWSume reads `~/.aws/config` and `~/.aws/credentials`, handles MFA or role assumption when needed, then sets variables such as `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`, `AWS_PROFILE`, and region variables.

AWSume stores its own configuration at `~/.awsume/config.yaml` by default, or `${XDG_CONFIG_HOME}/awsume/config.yaml` when XDG config is set. It also caches MFA-authenticated credentials under `~/.awsume/cache/` according to the official overview.

### パッケージ好きにとっての重要性

AWSume is important for package nerds because it highlights a packaging wrinkle: some command-line tools are not just executables, they must integrate with the parent shell. The install is only half the story; aliases, shell wrappers, and PATH behavior determine whether it actually works.

It also belongs to the larger AWS credential-helper family: focused tools that do not replace AWS CLI but make AWS CLI, SDKs, and arbitrary subprocesses easier to use safely with temporary credentials.

### タイムライン

- 2016: Public GitHub repository `trek10inc/awsume` created.
- 2019: v4.0.0-era tag/commit appears in the repository history.
- 2020: v4.5.0 release commit recorded.
- 2024: Official docs mention 4.5.x credential_process support and 4.4.x role-chaining improvements.

### Related projects

- AWS CLI and AWS SDKs consume the environment variables and shared credentials AWSume manages.
- AWS STS AssumeRole and GetSessionToken are the AWS API operations behind many AWSume workflows.
- awsume-console-plugin and other AWSume extras extend the core credential workflow.

### ソース

- <https://api.github.com/repos/trek10inc/awsume>
- <https://awsu.me/>
- <https://awsu.me/general/aws-file-configuration.html>
- <https://awsu.me/general/config.html>
- <https://awsu.me/general/overview.html>
- <https://awsu.me/general/quickstart.html>
- <https://github.com/trek10inc/awsume>


## セキュリティノート

awsume に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。



## 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: ~/.awsume/config.yaml, ${XDG_CONFIG_HOME}/awsume/config.yaml, ~/.aws/config

## Credential files

- Unix: ~/.aws/credentials
## 他のパッケージマネージャ記録

- Nix - awsume: normalized package name match | nixpkgs package indexes: pkgs/by-name/aw/awsume/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/awsume.yml](https://github.com/mxcl/pkgdb/blob/main/combined/awsume.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
