How does anyone use vagrant with AWS?

Vagrant
1

I’ve used vagrant for years, and been on teams using it for even longer. Pretty much always for use on AWS, and for development of some web app or cloud thing. AFAICT, this is a pretty common way to use vagrant, but there isn’t an actively supported plugin for AWS. Am I mistaken? Is the deprecated/archived aws plugin/github repo the thing to install? Are vagrant and AWS not a combination hashicorp recommend?

2

Hi… I wasn’t aware of the plugin, but I do code deployment from my Vagrant DEV instances in a flow order

  1. Code … Uses Vagrant to provision and run the dev environment
  2. Commits to the GitHub - Manual
  3. CI-CD workflow from GIT to reply to AWS EC2

Another way is to use CodeCommit in AWS. But as you say, using vagrant file and provider AWS

vagrant-aws

  1. Install Plugin

$ vagrant plugin install vagrant-aws

  1. Vagrant up, with was provider

$ vagrant up --provider=aws

Sample Vagrant File

3

With a recent version of Vagrant, it is no longer possible to install the aws provider plugin due to a dependency version clash:

$ vagrant plugin install vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:

conflicting dependencies excon (~> 0.6.1) and excon (= 1.2.0)
  Activated excon-1.2.0
  which does not match conflicting dependency (~> 0.6.1)

  Conflicting dependency chains:
    excon (= 1.2.0), 1.2.0 activated

  versus:
    vagrant-aws (> 0), 0.0.1 activated, depends on
    fog (>= 0.9.0), 0.9.0 activated, depends on
    excon (~> 0.6.1)

This seems to have been the case for a couple of years now. Is anyone even attempting to fix the problem?