mirror of
https://codeberg.org/scottslowe/learning-tools.git
synced 2026-03-11 09:04:37 +00:00
e039a4eb8e
Add files for a learning environment that supports spinning up multiple instances on AWS via Vagrant with the `vagrant-aws` provider.
35 lines
3 KiB
Markdown
35 lines
3 KiB
Markdown
# Using Vagrant with AWS (Multiple Instances)
|
|
|
|
These files were created to allow users to use Vagrant ([http://www.vagrantup.com](http://www.vagrantup.com)) with AWS, where the VMs managed by Vagrant are actually instances running on AWS. This environment can be used to spin up multiple instances. This configuration was tested using Vagrant 1.8.5, version 0.7.2 of [the vagrant-aws plugin](https://github.com/mitchellh/vagrant-aws), and AWS.
|
|
|
|
## Contents
|
|
|
|
* **instances.yml**: This YAML file contains the instance-specific configuration information. Four values are expected in this file: `name` (a friendly name for the instance, will _not_ be honored by AWS), `type` (the instance type, such as "m3.medium"), `ami`, and `user`.
|
|
|
|
* **README.md**: The file you're currently reading.
|
|
|
|
* **Vagrantfile**: This file is used by Vagrant to spin up the OpenStack instance. There are two changes that **must** be made to this file in order for it to function properly: you must specify the correct path to your SSH private key (the private key for the keypair specified in `instances.yml`), and you must supply the correct name to the dummy box installed for use with AWS.
|
|
|
|
## Instructions
|
|
|
|
These instructions assume that you have an AWS account, that you know your AWS access key ID and secret access key, and that you have a valid SSH keypair configured in your AWS account.
|
|
|
|
1. Vagrant requires that a "dummy box" be installed for use with AWS. Run this command to install the dummy box:
|
|
|
|
vagrant box add <box-name> https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
|
|
|
|
2. Install the Vagrant AWS provider by running `vagrant plugin install vagrant-aws`.
|
|
|
|
3. Place the files from the `vagrant-aws-multi` directory of this GitHub repository into a directory on your local system. You can clone the entire "learning-tools" repository (using `git clone`), download a ZIP file of the entire "learning-tools" repository, or just download the specific files from the the `vagrant-aws-multi` folder.
|
|
|
|
4. Edit `instances.yml` to supply the correct information to be used by Vagrant when launching an instance on AWS. You'll need to specify the friendly name, instance type, AMI ID, and default SSH user for the AMI.
|
|
|
|
5. In a terminal window, set the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables to your AWS access key ID and AWS secret access key, respectively.
|
|
|
|
7. In the directory where you placed the files from this GitHub repository, run `vagrant up` to have Vagrant authenticate to AWS and launch the desired instances for you. Once the instance is created, you can use `vagrant ssh <name>` to connect to a particular instance, and `vagrant destroy` will terminate (destroy) the AWS instances. (You can follow all these actions in the AWS Management Console, if you so desire.)
|
|
|
|
Enjoy!
|
|
|
|
## Additional Notes
|
|
|
|
This environment is a complement to the environment found in the `vagrant-aws` directory. That environment only allows you to spin up a single instance using Vagrant, whereas this environment supports the creation of multiple instances.
|