Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Support authentication when AWS environment variables are already available in the environment #101

Open
christophetd opened this issue Aug 11, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@christophetd
Copy link
Contributor

Using aws-vault to authenticate, it would be useful if cloudgoat could take into account the environment variables already available to authenticate to AWS rather than having to specify a profile.

$ aws sts get-caller-identity
{
    "UserId": "XXXXX:[email protected]",
    "Account": "123456789123",
    "Arn": "arn:aws:sts::123456789123:assumed-role/XXX/[email protected]"
}
$ ./cloudgoat.py create cloud_breach_s3
The create command requires the use of the --profile flag, or a default profile defined in the config.yml file (try "config profile").
@RyanJarv RyanJarv added the enhancement New feature or request label Aug 11, 2021
@RyanJarv
Copy link
Contributor

This would be a great change, this often effects me as well. Will look into changing this behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants