问题
Every time I want to config something with AWS I get the following error :
"The config profile (myname) could not be found"
like : aws configure
I'm using Python 3.4 and I want to use AWS CLI Keyring to encrypt my credentials..
回答1:
I think there is something missing from the AWS documentation in http://docs.aws.amazon.com/lambda/latest/dg/setup-awscli.html, it did not mention that you should edit the file ~/.aws/config to add your username profile. There are two ways to do this:
edit
~/.aws/configoraws configure --profile "your username"
回答2:
I ran into this problem when I moved to a new machine, carrying with me my AWS_DEFAULT_PROFILE environment variable, but not my ~/.aws directory. I couldn't get any awscli commands to work until I unset that variable or properly configured the named profile. But even the aws configure command was broken, making things a bit tricky. Assuming you have a Unix-like shell handy:
- To determine what AWS-specific variables you might have in your session:
env | grep AWS_- if you don't see AWS_DEFAULT_PROFILE listed here, this answer is not applicable to you.
- To temporarily remove the default profile:
unset AWS_DEFAULT_PROFILE - To configure that default profile:
aws --profile foo configure - To reset the default profile variable:
exec $SHELL - To test your new setup:
aws iam get-user
回答3:
can you check your config file under ~/.aws/config- you might have an invalid section called [myname], something like this (this is an example)
[default]
region=us-west-2
output=json
[myname]
region=us-east-1
output=text
Just remove the [myname] section (including all content for this profile) and you will be fine to run aws cli again
回答4:
Use as follows
[profilename]
region=us-east-1
output=text
Example cmd
aws --profile myname CMD opts
回答5:
Working with profiles is little tricky. Documentation can be found at: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html (But you need to pay attention on env variables like AWS_PROFILE)
Using profile with aws cli requires a config file (default at ~/.aws/config or set using AWS_CONFIG_FILE).
A sample config file for reference:
`
[profile PROFILE_NAME]
output=json
region=us-west-1
aws_access_key_id=foo
aws_secret_access_key=bar
`
Env variable AWS_PROFILE informs AWS cli about the profile to use from AWS config. It is not an alternate of config file like AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY are for ~/.aws/credentials.
Another interesting fact is if AWS_PROFILE is set and the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables are set, then the credentials provided by AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY will override the credentials located in the profile provided by AWS_PROFILE.
回答6:
Did you actually set up your specific user? The walkthrough setup guide in AWS explains how to set a default user, and then how to set up additional users. If you didn't complete the full setup, you'll just have a default block and your myName won't have been created..
回答7:
Was facing similar issue and found below link more helpful then the answers provided here. I guess this is due to the updates to AWS CLI since the answers are provided.
https://serverfault.com/questions/792937/the-config-profile-adminuser-could-not-be-found
Essentially it helps to create two different files (i.e. one for the general config related information and the second for the credentials related information).
回答8:
Make sure you are in the correct VirtualEnvironment. I updated PyCharm and for some reason had to point my project at my VE again. Opening the terminal, I was not in my VE when attempting zappa update (and got this error). Restarting PyCharm, all back to normal.
回答9:
For me it was because I had my .aws/config file looking like this:
[profile myname]
aws_access_key_id = ....
aws_secret_access_key = ....
region=us-west-1
I think the reason is I based it off my .aws/credentials file, which requires having [profile myname] for Zappa and maybe some other aws/elastic beanstalk tools.
When I changed config to this it worked great:
[myname]
aws_access_key_id = ....
aws_secret_access_key = ....
region=us-west-1
来源：https://stackoverflow.com/questions/34134879/aws-the-config-profile-myname-could-not-be-found