Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Amazon Web Services
  3. vagrant-aws

vagrant-aws

MITRuby

A Vagrant plugin that adds an AWS provider, enabling Vagrant to manage and provision EC2 and VPC instances.

GitHubGitHub
2.6k stars569 forks0 contributors

What is vagrant-aws?

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.

Target Audience

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.

Value Proposition

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.

Overview

Use Vagrant to manage your EC2 and VPC instances.

Use Cases

Best For

  • Managing AWS EC2 and VPC instances using Vagrant commands like 'vagrant up' and 'vagrant provision'.
  • Provisioning cloud instances with built-in Vagrant provisioners (e.g., Shell, Puppet, Chef) for consistent deployment.
  • Defining region-specific configurations to manage machines across multiple AWS regions from a single Vagrantfile.
  • Packaging running AWS instances into new Vagrant boxes for reuse and distribution.
  • Automatically attaching instances to Elastic Load Balancers (ELB) during boot and detaching on destroy.
  • Applying custom tags and user data scripts to AWS instances during provisioning for automation and organization.

Not Ideal For

  • Projects requiring advanced AWS networking setups like custom VPC routing or multiple network interfaces
  • Teams needing real-time, bidirectional folder synchronization for active development without manual rsync
  • Organizations that standardize on infrastructure-as-code tools like Terraform or AWS CloudFormation for all cloud resource management
  • Environments where minimal overhead and direct AWS CLI or SDK usage are preferred over Vagrant's abstraction layer

Pros & Cons

Pros

Familiar Vagrant Workflow

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.

Multi-Region Management

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.

Integrated Provisioning

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.

Instance Packaging

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.

Cons

Limited Networking Features

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.

Minimal Synced Folders

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.

Box Setup Overhead

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.

Frequently Asked Questions

Quick Stats

Stars2,591
Forks569
Contributors0
Open Issues243
Last commit5 years ago
CreatedSince 2013

Tags

#devops#vpc#ruby-gem#vagrant-plugin#infrastructure-as-code#aws#ec2#cloud-provisioning

Built With

R
Ruby
V
Vagrant

Included in

Amazon Web Services14.0k
Auto-fetched 1 day ago

Related Projects

cloud-custodiancloud-custodian

Rules engine for cloud security, cost optimization, and governance, DSL in yaml for policies to query, filter, and take actions on resources

Stars5,999
Forks1,622
Last commit4 days ago
nixopsnixops

NixOps is a tool for deploying to NixOS machines in a network or cloud.

Stars2,165
Forks365
Last commit5 months ago
aws-missing-toolsaws-missing-tools

tools for managing AWS resources including EC2, EBS, RDS, IAM, CloudFormation and Route53.

Stars1,336
Forks399
Last commit7 years ago
awspecawspec

RSpec tests for your AWS resources.

Stars1,177
Forks189
Last commit2 days ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub