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

Allow session name to be configure in config.yaml #100

Closed
choonming opened this issue May 15, 2020 · 5 comments
Closed

Allow session name to be configure in config.yaml #100

choonming opened this issue May 15, 2020 · 5 comments

Comments

@choonming
Copy link

choonming commented May 15, 2020

Whenever I want to assume a role via awsume, it will use my account name for the session. The user ID will appear as XXACCESSKEYIDXXX:account_name. I can fix this by adding --session name when running awsume but would it not be better if we can configure a default for all the awsume's parameter into the config.yaml?

colors: true
fuzzy-match: false
role-duration: 0
session-name: name
@mbarneyjr
Copy link
Member

mbarneyjr commented Jun 8, 2020

Hi @choonming ,

There is a ~/.aws/config file profile property called role_session_name, documented here: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html

Unfortunately, this property is not currently supported by awsume yet, but it's now on the list. Will support for this profile configuration property be sufficient for your use case or would a global default still be preferrable?

@choonming
Copy link
Author

choonming commented Jun 8, 2020

Hi @mbarneyjr ,

The property role_session_name do work if I'm not using awsume. If we set it both global default and per profile configuration in the configuration file, it'll be awesome. With the current awsume, It's rather difficult to identify the users on CloudTrail when everyone is assuming roles via awsume.

Even better if it can honor the properties in .aws/config

@mbarneyjr
Copy link
Member

mbarneyjr commented Jun 8, 2020

Sure thing, we'll be sure to support both in the next release, thanks for the bug report!

@mbarneyjr
Copy link
Member

mbarneyjr commented Aug 21, 2020

Hi, sorry for the delay in response! I've implemented this and a few other fixes. This should be found in pre release 4.5.0a1. I'll deploy this to release 4.5.0 once I'm confident in the changes. If you experience any issues with pre release 4.5.0a1 please update this issue, thanks!

@mbarneyjr
Copy link
Member

mbarneyjr commented Nov 20, 2020

Sorry for the delay, this has been deployed to 4.5.0

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

No branches or pull requests

2 participants