Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

aws.region is not loaded from Vagrantfile #473

Open
kenorb opened this issue Jun 26, 2016 · 4 comments · May be fixed by #484
Open

aws.region is not loaded from Vagrantfile #473

kenorb opened this issue Jun 26, 2016 · 4 comments · May be fixed by #484

Comments

@kenorb
Copy link

kenorb commented Jun 26, 2016

I've got Vagrantfile (linked before the change) where I've changed aws.region to us-west-1 (aws.region = "us-west-1"), but when creating a new instance, it's still showing my old region (us-east-1).

Launching an instance with the following settings...
 -- Type: t2.small
 -- AMI: ami-fce3c696
 -- Region: us-east-1

I've removed the region from ~/.aws/config, removed aws_profile and it didn't help. Is there any reason why would aws.region not be loaded directly from Vagrantfile?
@rtyler
Copy link
Collaborator

rtyler commented Jul 3, 2016

@kenorb Does your AMI exist in us-west-1? I have been successfully setting us-west-2 as my region for a long time. I just tried it again and did not see any issues :/

@kenorb
Copy link
Author

kenorb commented Jul 3, 2016

Thanks for reply.

I've tried to change to us-west-2/m3.medium (as per your file), but this error happened. Re-tested again changing the region, didn't work, Vagrant is reporting us-east-1 all the time.

I couldn't test any other AMI as per error above, I'll try again another time.

@mkubenka mkubenka linked a pull request Jul 27, 2016 that will close this issue
Open
@rocket-ron
Copy link

rocket-ron commented Aug 21, 2016 •
edited
Loading

I'm seeing several errors, including this one. The region is always us-east-1 and I can't seem to change it. It is set to us-west-1 in my ~/.aws/config file, and I can't set it in the Vagrant file. There is also an error specifying the keypair.

Follow up - if I place the aws.secret_access_key and aws.access_key_id in the Vagrantfile, then the region is also read from the Vagrantfile. Also this corrected the keypair issue I was seeing. So the problem seems to be when reading from the ~/.aws/config file? In any case, I'm attaching the DEBUG log output in case it's helpful.
vagrant_debug.txt

@kenorb
Copy link
Author

kenorb commented Aug 22, 2016

@rocket-ron You can test PR #484 if that helps.

elconde pushed a commit to elconde/vagrant-aws that referenced this issue Dec 2, 2020
@rconde-bt
Refs mitchellh#473 Don't lock the AWS region
d9800a1 
See the mitchellh#484 merge request
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow override region from Vagrantfile mkubenka/vagrant-aws
3 participants
@rtyler @kenorb @rocket-ron