mitchellh/vagrant-aws

Project Vargant and Vagrant-AWS plugin are dead

planesweep opened this issue · 4 comments

Hi,
in my opinion the project vagrant-aws plugin is dead. Currently there are 233 issues and 25 open pull requests.

Is there someone who feels responsible for the code?

Well Vagrant isn't dead by any stretch... but yes, this project looks like it's sunsetting :(

It does still work, just! If you have an existing project, upgrade to all the latest tooling (vagrant + plugins, chef, parallels) and apply the fixes detailed in this issue thread...

#365

But certainly not recommended for any new projects.

It is a shame because the AWS built-in solution, OpsWorks, works out ~$15p/month for a single instance. When a micro-instance capable of running a dozen low traffic websites can cost as little as $6-7 p/month - the OpsWorks management cost kills the economics. This plugin fitted very neatly for those simple, ultra low cost use cases.

+1
I moved to use terraform.

@planesweep I believe you just nominated yourself