Can AWS Credentials in Vagrantfile be programmatically grabbed?

[timvisher]

I'm trying to use vagrant for an open source project but I want to keep the people who can launch ec2 instances at a minimum. Is there any way to do this with vagrant aws?

[tralamazza]

Just use different AWS keypairs.
vagrant-aws itself has no user access control

[timvisher]

How can I check the Vagrantfile in to a public repository, though? That's the real question. My use case is that I'd like people to be able to provision a local VirtualBox VM using the same Vagrantfile but then have anyone with ec2 creds be able to set them in their environment or something and launch an ec2 instance using vagrant-aws.

[tralamazza]

hmm, I think you can have a conditional statement inside your unified Vagrantfile that would search for an env var, and use the proper provider accordingly. People with those env vars would launch on EC2, else plain local vbox. I will try this later and post my findings here.

[rajivr]

@tralamazza You might want to check out the approach taken by aws-sdk

https://github.com/aws/aws-sdk-ruby/blob/master/lib/aws/core/credential_providers.rb#L89

[erran]

@timvisher You could probably use multiple Vagrantfiles and make the conditionals based on AWS environment variables.

[zelig]

see also #182

[rtyler]

I think this is a good thing to allow to be stuck into a file in .vagrant/, I'll pull it in to the next milestone

[msgilligan]

+1 on creating a file inside ~/.vagrant -- I use that approach with build.gradle files and it works reasonably well.

[sursh]

Someone made a little plugin that handles this problem https://github.com/maoueh/nugrant