-
Notifications
You must be signed in to change notification settings - Fork 283
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
Support for --region and --profile #16
Comments
I'd love to see this support also. You can split the profile into |
Great suggestion! Currently you'd have to specify region or profile like the following:
I agree, I think supporting a config for |
What first came to my mind was more of: As mattford63 mentioned, you can have the profiles (along with default regions per profile making the |
Thanks for clarifying! |
You can also set the environment variable AWS_DEFAULT_PROFILE, meaning you no longer have to specify the profile for every command. |
I found this works
|
In the meantime, I'll update the README installation section: AWS Credentials and Named ProfilesConfigure your credentials with the AWS CLI:
If you'd like to use a specific named profile with
Or as a one-liner:
Windows users can run the following commands:
Command line options for starting For more details on how to install and configure the AWS CLI, refer to the following documentation. |
+1 |
I'm using 0.4.3, have my region set in an environment variable and profile, and while it's using the correct version it still says |
Could we have the feature as
more than |
The AWS config file allows for multiple profiles and specifying a particular region if you're in more than one. This allows for having a single configuration file which holds credentials for multiple AWS accounts.
As I've got the [default] entry disabled by default, saws wouldn't function properly. At the moment I've set a particular profile and region as a default just to play around, and it looks pretty nice, but being able to specify profile and region when launching saws would be hugely helpful. (Alternately, if the functionality exists, and I just couldn't figure it out...my apologies.)
The text was updated successfully, but these errors were encountered: