Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Casbin | 14,109 | 462 | 2 days ago | 210 | September 20, 2022 | 22 | apache-2.0 | Go | ||
An authorization library that supports access control models like ACL, RBAC, ABAC in Golang | ||||||||||
Aws Vault | 7,360 | 1 | 4 | 2 days ago | 78 | March 08, 2022 | 44 | mit | Go | |
A vault for securely storing and accessing AWS credentials in development environments | ||||||||||
Aws Iam Authenticator | 1,970 | 45 | 16 days ago | 27 | July 01, 2022 | 17 | apache-2.0 | Go | ||
A tool to use AWS IAM credentials to authenticate to a Kubernetes cluster | ||||||||||
Kube2iam | 1,884 | 2 months ago | 2 | March 10, 2021 | 105 | bsd-3-clause | Go | |||
kube2iam provides different AWS IAM roles for pods running on Kubernetes | ||||||||||
Configure Aws Credentials | 1,730 | a day ago | 41 | mit | JavaScript | |||||
Configure AWS credential environment variables for use in other GitHub Actions. | ||||||||||
Pmapper | 1,152 | 5 months ago | 8 | January 13, 2022 | 20 | agpl-3.0 | Python | |||
A tool for quickly evaluating IAM permissions in AWS. | ||||||||||
Kiam | 1,131 | a month ago | 1 | July 07, 2021 | 121 | apache-2.0 | Go | |||
Integrate AWS IAM with Kubernetes | ||||||||||
Rbac Lookup | 718 | 16 days ago | 30 | July 06, 2022 | 8 | apache-2.0 | Go | |||
Easily find roles and cluster roles attached to any user, service account, or group name in your Kubernetes cluster | ||||||||||
Cloudtracker | 660 | 2 years ago | 6 | March 21, 2020 | 18 | bsd-3-clause | Python | |||
CloudTracker helps you find over-privileged IAM users and roles by comparing CloudTrail logs with current IAM policies. | ||||||||||
Terraform Aws Iam | 607 | 2 days ago | 8 | apache-2.0 | HCL | |||||
Terraform module which creates IAM resources on AWS 🇺🇦 |
Rapture is a shell-integrated CLI tool for assuming AWS IAM roles easily and quickly.
$ rapture whoami
arn:aws:iam::999988887777:user/janesmith
$ rapture alias set admin arn:aws:iam::000011110000:role/admin-power
alias 'admin' was set to 'arn:aws:iam::000011110000:role/admin-power'
$ rapture alias ls
arn:aws:iam::000011110000:role/admin-power admin
arn:aws:iam::302830283028:role/marketing-access marketing
$ rapture assume admin
Assumed role 'arn:aws:iam::000011110000:role/admin-power'
$ rapture whoami
arn:aws:sts::000011110000:assumed-role/admin-power/rapture-janesmith
$ rapture resume
Resumed base credentials
$ rapture whoami
arn:aws:iam::999988887777:user/janesmith
First, install the latest Rapture binary for your platform from Github and copy it to a directory in your PATH. Or if you prefer you can build it yourself (Go 1.12 or higher required):
$ go install github.com/daveadams/go-rapture/cmd/[email protected]
To configure your shell to load Rapture at startup, follow the instructions below for your specific shell.
In your shell startup file (usually ~/.bash_profile
or ~/.bashrc
; for Zsh
usually ~/.zshrc
), add the following line:
eval "$( command rapture shell-init )"
In your Fish startup file (~/.config/fish/config.fish
), add the following line:
eval ( command rapture shell-init )
Finally, open a new terminal window to verify that Rapture is automatically loaded:
$ rapture check
OK: Rapture is set up correctly
Simply remove the command source ~/.rapture/rapture.sh
from your shell startup
script, and replace it with the new command mentioned above. The old Rapture
configuration files will continue to work in the same way.
No configuration is required to start using Rapture, but Rapture will store
configuration in config.json
, aliases.json
, and accounts.json
in the
~/.rapture
directory.
Rapture exports the RAPTURE_ROLE
environment variable with the user-supplied
identifier of the currently-assumed role, either the role alias, or the ARN.
Rapture also exports the RAPTURE_ASSUMED_ROLE_ARN
environment variable to
the full ARN of the currently assumed role.
Both of these environment variables are unset when base credentials are loaded.
Rapture does not manage your secrets for you. But Rapture is integrated with Vaulted for providing secure storage of AWS access keys (and other secrets) in an easily manageable format and for loading them into your environment.
If you have your AWS credentials configured in a vault named default
, then
you can simply run:
$ rapture init
This will run vaulted
on your behalf to load the credentials from the default
Vault into your current environment. Or you can specify a different vault name:
$ rapture init awsvault
If you set a value for default_vault
in ~/.rapture/config.json
, Rapture
will use that name instead of default
as the default vault to decrypt.
This software is public domain. No rights are reserved. See LICENSE for more information.