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
"awsume [profile-name]" command hangs and never responds #117
Comments
I have the same issue on MacOS Catalina version 10.15.6. It works with User profiles, but for all Role the awsume python process draws about 100% CPU (one core). |
After this it hangs for ever... |
I figured it out. You can't have a profile in .aws/config that have the same name as a credentials in ./aws/credentials if it has a source_profile with the same name... added an suffix to the user accounts config solved the issue. So the bug is in how awsume tries to resolve infinity roles. Support added in "Adds support for infinite role-chaining" on line 235 of app.py PR |
Hi! Thanks for opening this issue, sorry about the delay! The # ~/.aws/credentials
[myuser]
aws_access_key_id = ...
aws_secret_access_key = ...
# ~/.aws/config
[profile myuser]
region = ...
[profile myrole]
role_arn = ...
source_profile = ...
region = ... Awsume should raise an error if the @cameronbesse Just to confirm, was @skjutare's solution solve your problem? |
@mbarneyjr Yes, I had the same issue in my credentials file. |
Hmm, I seem to be having trouble replicating the issue. Correct me if I'm misunderstanding your setup, but if I create the following profile configuration: #~/.aws/credentials
[test]
aws_access_key_id = ...
aws_secret_access_key = ...
#~/.aws/config
[profile test]
source_profile = test I correctly get the following error: $ awsume test
Awsume error: Invalid profile [test] cannot have circular role-chains If you're able to replicate the error, could you show your profile setup (redacting any secrets and account IDs, of course)? Thank you! |
With a similar setup to this I can get it to hang
while calling |
Great, that was what I needed to find the bug, thanks! It should be fixed in pre release 4.5.0a2 |
Sorry for the delay, this has been deployed to 4.5.0 |
I have installed awsume via pip and I have the correct alias in my bash profile. Awsume does correctly list my available AWS profiles with
awsume -l
, however when I try to use theawsume [profile-name]
command to assume a profile, the terminal hangs and there is no response.(On MacOS Catalina version 10.15.5 (19F101), using iTerm2 build 3.3.12)
The text was updated successfully, but these errors were encountered: