devtanc
Doesn't modify or read the ~/.aws/config file
The ~/.aws/config file, if present, could cause unexpected behavior, or complete failure. See the info for the file here.
Some important bits here:
Storing Credentials in Config The AWS CLI will also read credentials from the config file. If you want to keep all of your profile settings in a single file, you can. If there are ever credentials in both locations for a profile (say you used aws configure to update the profile's keys), the keys in the credentials file will take precedence. If you use one of the SDKs in addition to the AWS CLI, you may notice additional warnings if credentials are not stored in their own file.
The AWS CLI supports named profiles stored in the config and credentials files. You can configure additional profiles by using aws configure with the --profile option or by adding entries to the config and credentials files.
Important The AWS credentials file uses a different naming format than the CLI config file for named profiles. Do not include the 'profile ' prefix when configuring a named profile in the AWS credentials file.
Add support for the config file in PR https://github.com/devtanc/aws-profile-switcher/pull/4
