Open ryanschmidt opened 7 years ago
This one just bit me as well, trying to use AWS provider on an AWS hosted instance. Even though the EC2 instance has the proper role and permissions, it asks me to provide keys.
I'm getting the following error when attempting to use an attached role:
There are errors in the configuration of this machine. Please fix
the following errors and try again:
AWS Provider:
* One or more of the needed AWS credentials are missing. No environment variables
are set nor profile 'default' exists at '/home/ec2-user/.aws/'
I was able to get around the use_iam_profile
bug by adding a dummy secret and key to my Vagrantfile:
aws.use_iam_profile = true
aws.access_key_id = "dummy_access_key"
aws.secret_access_key = "dummy_secret_key"
Will do this until https://github.com/mitchellh/vagrant-aws/pull/525 is merged.
Is anyone using
use_iam_profile
successfully? I've not been able to get it to work as I would expect and some searching turned up some threads that make me think that it may not actually work.Does fog-aws actually require secret_access_key & access_key_id? If so, I'm not sure how vagrant-aws can work considering when
use_iam_profle
is set to true we don't send those credentials.Any leads would be appreciated!