[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7948":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":15,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":16,"rankGlobal":9,"rankLanguage":9,"license":17,"archived":18,"fork":19,"defaultBranch":20,"hasWiki":18,"hasPages":19,"topics":21,"createdAt":9,"pushedAt":9,"updatedAt":22,"readmeContent":23,"aiSummary":24,"trendingCount":15,"starSnapshotCount":15,"syncStatus":25,"lastSyncTime":26,"discoverSource":27},7948,"vagrant-aws","mitchellh\u002Fvagrant-aws","mitchellh","Use Vagrant to manage your EC2 and VPC instances.",null,"Ruby",2591,569,2593,243,0,30.27,"MIT License",true,false,"master",[],"2026-06-12 02:01:46","# Vagrant AWS Provider\n[![Gitter](https:\u002F\u002Fbadges.gitter.im\u002FJoin Chat.svg)](https:\u002F\u002Fgitter.im\u002Fmitchellh\u002Fvagrant-aws?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n\n\u003Cspan class=\"badges\">\n[![Gem Version](https:\u002F\u002Fbadge.fury.io\u002Frb\u002Fvagrant-aws.png)][gem]\n[![Dependency Status](https:\u002F\u002Fgemnasium.com\u002Fmitchellh\u002Fvagrant-aws.png)][gemnasium]\n\u003C\u002Fspan>\n\n[gem]: https:\u002F\u002Frubygems.org\u002Fgems\u002Fvagrant-aws\n[gemnasium]: https:\u002F\u002Fgemnasium.com\u002Fmitchellh\u002Fvagrant-aws\n\nThis is a [Vagrant](http:\u002F\u002Fwww.vagrantup.com) 1.2+ plugin that adds an [AWS](http:\u002F\u002Faws.amazon.com)\nprovider to Vagrant, allowing Vagrant to control and provision machines in\nEC2 and VPC.\n\n**NOTE:** This plugin requires Vagrant 1.2+,\n\n## Features\n\n* Boot EC2 or VPC instances.\n* SSH into the instances.\n* Provision the instances with any built-in Vagrant provisioner.\n* Minimal synced folder support via `rsync`.\n* Define region-specific configurations so Vagrant can manage machines\n  in multiple regions.\n* Package running instances into new vagrant-aws friendly boxes\n\n## Usage\n\nInstall using standard Vagrant 1.1+ plugin installation methods. After\ninstalling, `vagrant up` and specify the `aws` provider. An example is\nshown below.\n\n```\n$ vagrant plugin install vagrant-aws\n...\n$ vagrant up --provider=aws\n...\n```\n\nOf course prior to doing this, you'll need to obtain an AWS-compatible\nbox file for Vagrant.\n\n## Quick Start\n\nAfter installing the plugin (instructions above), the quickest way to get\nstarted is to actually use a dummy AWS box and specify all the details\nmanually within a `config.vm.provider` block. So first, add the dummy\nbox using any name you want:\n\n```\n$ vagrant box add dummy https:\u002F\u002Fgithub.com\u002Fmitchellh\u002Fvagrant-aws\u002Fraw\u002Fmaster\u002Fdummy.box\n...\n```\n\nAnd then make a Vagrantfile that looks like the following, filling in\nyour information where necessary.\n\n```\nVagrant.configure(\"2\") do |config|\n  config.vm.box = \"dummy\"\n\n  config.vm.provider :aws do |aws, override|\n    aws.access_key_id = \"YOUR KEY\"\n    aws.secret_access_key = \"YOUR SECRET KEY\"\n    aws.session_token = \"SESSION TOKEN\"\n    aws.keypair_name = \"KEYPAIR NAME\"\n\n    aws.ami = \"ami-7747d01e\"\n\n    override.ssh.username = \"ubuntu\"\n    override.ssh.private_key_path = \"PATH TO YOUR PRIVATE KEY\"\n  end\nend\n```\n\nAnd then run `vagrant up --provider=aws`.\n\nThis will start an Ubuntu 12.04 instance in the us-east-1 region within\nyour account. And assuming your SSH information was filled in properly\nwithin your Vagrantfile, SSH and provisioning will work as well.\n\nNote that normally a lot of this boilerplate is encoded within the box\nfile, but the box file used for the quick start, the \"dummy\" box, has\nno preconfigured defaults.\n\nIf you have issues with SSH connecting, make sure that the instances\nare being launched with a security group that allows SSH access.\n\nNote: if you don't configure `aws.access_key_id` or `aws_secret_access_key`\nit will attempt to read credentials from environment variables first and then\nfrom `$HOME\u002F.aws\u002F`. You can choose your AWS profile and files location by using\n`aws.aws_profile` and `aws.aws_dir`, however environment variables will always\nhave precedence as defined by the [AWS documentation](http:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Fuserguide\u002Fcli-chap-getting-started.html).\nTo use profile `vagrantDev` from your AWS files:\n```ruby\n  # this first line can actually be omitted\n  aws.aws_dir = ENV['HOME'] + \"\u002F.aws\u002F\"\n  aws.aws_profile = \"vagrantDev\"\n```\n\n\n## Box Format\n\nEvery provider in Vagrant must introduce a custom box format. This\nprovider introduces `aws` boxes. You can view an example box in\nthe [example_box\u002F directory](https:\u002F\u002Fgithub.com\u002Fmitchellh\u002Fvagrant-aws\u002Ftree\u002Fmaster\u002Fexample_box).\nThat directory also contains instructions on how to build a box.\n\nThe box format is basically just the required `metadata.json` file\nalong with a `Vagrantfile` that does default settings for the\nprovider-specific configuration for this provider.\n\n## Configuration\n\nThis provider exposes quite a few provider-specific configuration options:\n\n* `access_key_id` - The access key for accessing AWS\n* `ami` - The AMI id to boot, such as \"ami-12345678\"\n* `availability_zone` - The availability zone within the region to launch\n  the instance. If nil, it will use the default set by Amazon.\n* `aws_profile` - AWS profile in your config files. Defaults to *default*.\n* `aws_dir` - AWS config and credentials location. Defaults to *$HOME\u002F.aws\u002F*.\n* `instance_ready_timeout` - The number of seconds to wait for the instance\n  to become \"ready\" in AWS. Defaults to 120 seconds.\n* `instance_check_interval` - The number of seconds to wait to check the instance's\n state\n* `instance_package_timeout` - The number of seconds to wait for the instance\n  to be burnt into an AMI during packaging. Defaults to 600 seconds.\n* `instance_type` - The type of instance, such as \"m3.medium\". The default\n  value of this if not specified is \"m3.medium\".  \"m1.small\" has been\n  deprecated in \"us-east-1\" and \"m3.medium\" is the smallest instance\n  type to support both paravirtualization and hvm AMIs\n* `keypair_name` - The name of the keypair to use to bootstrap AMIs\n   which support it.\n* `monitoring` - Set to \"true\" to enable detailed monitoring.\n* `session_token` - The session token provided by STS\n* `private_ip_address` - The private IP address to assign to an instance\n  within a [VPC](http:\u002F\u002Faws.amazon.com\u002Fvpc\u002F)\n* `elastic_ip` - Can be set to 'true', or to an existing Elastic IP address. \n  If true, allocate a new Elastic IP address to the instance. If set\n  to an existing Elastic IP address, assign the address to the instance.\n* `region` - The region to start the instance in, such as \"us-east-1\"\n* `secret_access_key` - The secret access key for accessing AWS\n* `security_groups` - An array of security groups for the instance. If this\n  instance will be launched in VPC, this must be a list of security group\n  Name. For a nondefault VPC, you must use security group IDs instead (http:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fec2\u002Frun-instances.html).\n* `iam_instance_profile_arn` - The Amazon resource name (ARN) of the IAM Instance\n    Profile to associate with the instance\n* `iam_instance_profile_name` - The name of the IAM Instance Profile to associate\n  with the instance\n* `subnet_id` - The subnet to boot the instance into, for VPC.\n* `associate_public_ip` - If true, will associate a public IP address to an instance in a VPC.\n* `ssh_host_attribute` - If `:public_ip_address`, `:dns_name`, or\n  `:private_ip_address`, will use the public IP address, DNS name, or private\n  IP address, respectively, to SSH to the instance. By default Vagrant uses the\n  first of these (in this order) that is known. However, this can lead to\n  connection issues if, e.g., you are assigning a public IP address but your\n  security groups prevent public SSH access and require you to SSH in via the\n  private IP address; specify `:private_ip_address` in this case.\n* `tenancy` - When running in a VPC configure the tenancy of the instance.  Supports 'default' and 'dedicated'.\n* `tags` - A hash of tags to set on the machine.\n* `package_tags` - A hash of tags to set on the ami generated during the package operation.\n* `use_iam_profile` - If true, will use [IAM profiles](http:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Finstance-profiles.html)\n  for credentials.\n* `block_device_mapping` - Amazon EC2 Block Device Mapping Property\n* `elb` - The ELB name to attach to the instance.\n* `unregister_elb_from_az` - Removes the ELB from the AZ on removal of the last instance if true (default). In non default VPC this has to be false.\n* `terminate_on_shutdown` - Indicates whether an instance stops or terminates\n  when you initiate shutdown from the instance.\n* `endpoint` - The endpoint URL for connecting to AWS (or an AWS-like service). Only required for non AWS clouds, such as [eucalyptus](https:\u002F\u002Fgithub.com\u002Feucalyptus\u002Feucalyptus\u002Fwiki).\n\nThese can be set like typical provider-specific configuration:\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider :aws do |aws|\n    aws.access_key_id = \"foo\"\n    aws.secret_access_key = \"bar\"\n  end\nend\n```\n\nNote that you do not have to hard code your `aws.access_key_id` or `aws.secret_access_key`\nas they will be retrieved from the enviornment variables `AWS_ACCESS_KEY` and `AWS_SECRET_KEY`.\n\nIn addition to the above top-level configs, you can use the `region_config`\nmethod to specify region-specific overrides within your Vagrantfile. Note\nthat the top-level `region` config must always be specified to choose which\nregion you want to actually use, however. This looks like this:\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider :aws do |aws|\n    aws.access_key_id = \"foo\"\n    aws.secret_access_key = \"bar\"\n    aws.region = \"us-east-1\"\n\n    # Simple region config\n    aws.region_config \"us-east-1\", :ami => \"ami-12345678\"\n\n    # More comprehensive region config\n    aws.region_config \"us-west-2\" do |region|\n      region.ami = \"ami-87654321\"\n      region.keypair_name = \"company-west\"\n    end\n  end\nend\n```\n\nThe region-specific configurations will override the top-level\nconfigurations when that region is used. They otherwise inherit\nthe top-level configurations, as you would probably expect.\n\n## Networks\n\nNetworking features in the form of `config.vm.network` are not\nsupported with `vagrant-aws`, currently. If any of these are\nspecified, Vagrant will emit a warning, but will otherwise boot\nthe AWS machine.\n\n## Synced Folders\n\nThere is minimal support for synced folders. Upon `vagrant up`,\n`vagrant reload`, and `vagrant provision`, the AWS provider will use\n`rsync` (if available) to uni-directionally sync the folder to\nthe remote machine over SSH.\n\nSee [Vagrant Synced folders: rsync](https:\u002F\u002Fdocs.vagrantup.com\u002Fv2\u002Fsynced-folders\u002Frsync.html)\n\n\n## Other Examples\n\n### Tags\n\nTo use tags, simply define a hash of key\u002Fvalue for the tags you want to associate to your instance, like:\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider \"aws\" do |aws|\n    aws.tags = {\n\t  'Name' => 'Some Name',\n\t  'Some Key' => 'Some Value'\n    }\n  end\nend\n```\n\n### User data\n\nYou can specify user data for the instance being booted.\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider \"aws\" do |aws|\n    # Option 1: a single string\n    aws.user_data = \"#!\u002Fbin\u002Fbash\\necho 'got user data' > \u002Ftmp\u002Fuser_data.log\\necho\"\n\n    # Option 2: use a file\n    aws.user_data = File.read(\"user_data.txt\")\n  end\nend\n```\n\n### Disk size\n\nNeed more space on your instance disk? Increase the disk size.\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider \"aws\" do |aws|\n    aws.block_device_mapping = [{ 'DeviceName' => '\u002Fdev\u002Fsda1', 'Ebs.VolumeSize' => 50 }]\n  end\nend\n```\n\n### ELB (Elastic Load Balancers)\n\nYou can automatically attach an instance to an ELB during boot and detach on destroy.\n\n```ruby\nVagrant.configure(\"2\") do |config|\n  # ... other stuff\n\n  config.vm.provider \"aws\" do |aws|\n    aws.elb = \"production-web\"\n  end\nend\n```\n\n## Development\n\nTo work on the `vagrant-aws` plugin, clone this repository out, and use\n[Bundler](http:\u002F\u002Fgembundler.com) to get the dependencies:\n\n```\n$ bundle\n```\n\nOnce you have the dependencies, verify the unit tests pass with `rake`:\n\n```\n$ bundle exec rake\n```\n\nIf those pass, you're ready to start developing the plugin. You can test\nthe plugin without installing it into your Vagrant environment by just\ncreating a `Vagrantfile` in the top level of this directory (it is gitignored)\nand add the following line to your `Vagrantfile` \n```ruby\nVagrant.require_plugin \"vagrant-aws\"\n```\nUse bundler to execute Vagrant:\n```\n$ bundle exec vagrant up --provider=aws\n```\n","vagrant-aws 是一个 Vagrant 插件，允许用户通过 Vagrant 管理和配置 AWS EC2 和 VPC 实例。其核心功能包括启动 EC2 或 VPC 实例、SSH 连接到实例、使用内置的 Vagrant 配置工具进行实例配置以及支持跨区域管理。该插件还提供了基本的同步文件夹支持，并能够将运行中的实例打包成新的 vagrant-aws 友好的 box 文件。适用于需要在 AWS 云环境中快速部署和管理开发环境的场景，特别适合那些已经熟悉 Vagrant 工作流的开发者或团队。",2,"2026-06-11 03:15:20","top_language"]