-
Notifications
You must be signed in to change notification settings - Fork 279
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
SAWS Caching credentials? Leading to conflict. #62
Comments
@zapman449 have you tried setting AWS Credentials and Named ProfilesIf you'd like to use a specific named profile with
Or as a one-liner:
|
I have not. Due to other aspects of our tooling, I'm hoping that SAWS can use the same auth mechanisms that AWSCLI can... The AWSCLI documentation says that the Shell Variables trump any config files. Further, it's still very odd that SAWS is able to tab complete something that's not in the account that the internal AWS command will use Example: Account B s3 buckets: AWS variables set to Account A saws List will show: But 'aws s3 ls' will only work with account A's buckets. -Jason |
@zapman449 it does seem like the there's an issue with I appreciate the detailed info, it should help investigating and fixing the root cause. |
When I set shell variables AWS_SECRET_ACCESS_ID and AWS_ACCESS_KEY_ID, and within SAWS run a command like:
aws s3 ls s3://
The command works
However, tab-completion is attempting to work against a DIFFERENT account, which is confusing as heck.
Does SAWS cache a credential or token somewhere if you run "aws configure"?
I don't see anything interesting in .saws-history or .saws.log or .sawsrc
-Jason
The text was updated successfully, but these errors were encountered: