search

WhoopInc / vagrant-s3auth

Vagrant plugin for private, versioned boxes on Amazon S3.
MIT License
108 stars 23 forks source link

Network unreachable error if credentials not found #15

Closed companykitchen-dev closed 9 years ago

companykitchen-dev commented 9 years ago

I had a configuration problem with my credentials file. This was user error. However, this causes the AWS apis to look for me credentials via the ec2 mechanism that is a hard coded IP and I got a network unreachable error. It would be nice to get a clearer error.

benesch commented 9 years ago

I'm unable to reproduce. I get the following error, as expected, when I don't have credentials configured properly:

Unable to read AWS credentials from the environment.

Ensure the following variables are set in your environment, or set
them at the top of your Vagrantfile:

    AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY

Can you provide more detail on your particular misconfiguration?

companykitchen-dev commented 9 years ago

Thanks for looking into it. I run windows and do almost all of my command line stuff via Cygwin. I am using the credentials file approach rather than environment variables. I had placed my credentials file in my windows home directory but Cygwin has it's own home directory. When I moved the credentials file to my Cygwin folder, everything works. I do have the line: #ENV['AWS_PROFILE'] = 'vagrant-s3auth' in my Vagrant file. Is it possible that setting caused it to take a different path that was fully vaidated?

benesch commented 9 years ago

Oops, no, I just didn't look hard enough! Looks like it always tries to hit the EC2 metadata IP—I've just never run the plugin without internet and so never ran into the issue.

benesch commented 9 years ago

Looks like upgrading to v2 of the API (releasing as vagrant-s3auth 1.1 shortly) will fix it.

Reopen if that's not the case!