A Vagrant plugin that adds an AWS provider, enabling Vagrant to manage and provision EC2 and VPC instances.
Vagrant AWS Provider is a plugin for Vagrant 1.2+ that extends Vagrant's capabilities to control and provision machines within Amazon Web Services (AWS) EC2 and VPC environments. It allows developers to use familiar Vagrant workflows to manage cloud infrastructure, bridging the gap between local development and cloud deployment.
Developers and DevOps engineers who use Vagrant for local development and want to manage AWS EC2 or VPC instances with the same workflow. It is particularly useful for teams needing consistent provisioning and configuration across local and cloud environments.
Developers choose this plugin because it brings Vagrant's simplicity and consistency to AWS infrastructure management, allowing them to treat cloud instances like local virtual machines. It supports multi-region configurations, instance packaging into reusable boxes, and integrates with existing Vagrant provisioners.
Use Vagrant to manage your EC2 and VPC instances.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses standard Vagrant commands like 'vagrant up' and 'vagrant provision' for AWS instances, reducing the learning curve for existing Vagrant users. The README shows integration with provider-specific configuration blocks in Vagrantfile.
Supports defining region-specific configurations within a single Vagrantfile using the region_config method, enabling easy control of instances across multiple AWS regions without separate setups.
Allows the use of any built-in Vagrant provisioner (e.g., Shell, Puppet) on AWS instances, ensuring consistent deployment scripts. The features list confirms SSH and provisioning support.
Enables packaging running instances into reusable Vagrant boxes with customizable tags via package_tags, facilitating image management and distribution as detailed in the configuration section.
Networking via config.vm.network is not supported, as admitted in the README, which restricts complex VPC setups and requires workarounds for advanced networking needs.
Only supports uni-directional folder syncing via rsync on specific commands, lacking real-time or bidirectional sync, which can be inconvenient for development workflows requiring frequent file updates.
Requires using a dummy box or custom box creation for initial setup, adding complexity compared to native AWS tools. The quick start section involves manual configuration of credentials and keys.