You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently in the process of making the switch from AWS Vault to Granted. I'm loving it so far!
In some of my shell scripts, I used to check for $AWS_VAULT, to ensure I was running the script through aws-vault exec (equivalent to assume --exec), so I could:
Give human friendly errors early, rather than fail with some IAM error further down the script.
Print the profile name before doing a dangerous action, so the user has a final chance to abort if they accidentally assumed the wrong role.
Is there a way to do this with Granted? I noticed there's no environment variable set during --exec that contains the profile name.
I guess I could parse it out of the Arn I see when I run aws sts get-caller-identity, but that doesn't describe the account as well as the SSO profile name. It was a nice convenience that AWS Vault used to provide. Is there a simple way to see the profile name, that I'm perhaps missing?
The text was updated successfully, but these errors were encountered:
Hello there,
I'm currently in the process of making the switch from AWS Vault to Granted. I'm loving it so far!
In some of my shell scripts, I used to check for
$AWS_VAULT
, to ensure I was running the script throughaws-vault exec
(equivalent toassume --exec
), so I could:Is there a way to do this with Granted? I noticed there's no environment variable set during
--exec
that contains the profile name.I guess I could parse it out of the
Arn
I see when I runaws sts get-caller-identity
, but that doesn't describe the account as well as the SSO profile name. It was a nice convenience that AWS Vault used to provide. Is there a simple way to see the profile name, that I'm perhaps missing?The text was updated successfully, but these errors were encountered: