aws.region is not loaded from Vagrantfile

[kenorb]

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]

@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]

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.

[rocket-ron]

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]

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