Repo brief: mitchellh/vagrant-aws

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T07:47:48.600Z · commit 43e7ec2eb425

Verdict

Mixed — Stale — last commit 5y ago

• 26+ active contributors
• Distributed ownership (top contributor 38% of recent commits)
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

vagrant-aws is a Vagrant provider plugin (Ruby) that enables Vagrant to manage EC2 and VPC instances on AWS as if they were local VMs. Instead of provisioning to VirtualBox or VMware, vagrant up --provider=aws boots real AWS instances, handles SSH access, and integrates with Vagrant's provisioning pipeline. It bridges the gap between Vagrant's local-first workflow and cloud infrastructure. The plugin uses Vagrant's action-based provider architecture: lib/vagrant-aws/action/ contains granular action classes (run_instance.rb, stop_instance.rb, connect_aws.rb, etc.) that chain together to handle lifecycle operations. Configuration is centralized in lib/vagrant-aws/config.rb, provider logic…

Start here

Open these first:

• lib/vagrant-aws/plugin.rb — Entry point that registers the AWS provider plugin with Vagrant; all Vagrant integration starts here.
• lib/vagrant-aws/provider.rb — Core provider class implementing Vagrant's provider interface; orchestrates all machine lifecycle operations.
• lib/vagrant-aws/action.rb — Action middleware builder that chains individual AWS operations; defines the state machine for instance management.
• lib/vagrant-aws/config.rb — Configuration schema for AWS provider settings (region, AMI, instance type, etc.); all user inputs validate here.
• lib/vagrant-aws/action/connect_aws.rb — Establishes AWS API client connection; foundational for all subsequent AWS API calls in the action chain.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

No Gemfile.lock or specific version constraints are visible. To set up locally: (1) clone the repo, (2) verify you have Ruby installed, (3) run bundle install (Gemfile is present), (4) run bundle exec rake spec to r…

Daily commands:

This is a plugin, not a standalone server. To test it: (1) vagrant plugin install ./ to install from local source, (2) create a Vagrantfile with config.vm.provider :aws block (see README example), (3) set AWS creden…

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 5y ago
• Scorecard: marked unmaintained (0/10)
• Scorecard: default branch unprotected (0/10)
• (1) AWS credentials: [REDACTED] plugin reads from environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY) or ~/.aws/credentials — if neither is set, it will fail silently at connect time. (2) Security groups:…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.