You may have seen the announcement that CentOS Atomic Host 15.10 is now available ( if not, go read the announcement here : http://seven.centos.org/2015/10/new-centos-atomic-host-release-available-now/ ).
What I’ve also done this time is create a vagrant_aws box that references the AMIs in the regions they are published. This is hand crafted and really just a PoC like effort, but if its something people find helpful I can plumb this into the main image generation process and ensure we get this done for every release.
Once you have vagrant running on your machine, you will need the vagrant_aws plugin. You can install this with:
vagrant plugin install aws”
and check its there with a
vagrant plugin list“.
You can then add the box with “
vagrant box add centos/atomic-host-aws“. Before we can instantiate the box, we need a local config with the aws credentials. So create a directory, and add the following into a Vagrantfile there :
Vagrant.configure(2) do |config| config.vm.box = "centos/atomic-host-aws" config.vm.provider :aws do |aws, override| aws.access_key_id = "Your AWS EC2 Key" aws.secret_access_key = "Your Secret Key" aws.keypair_name = "Your keypair name" override.ssh.private_key_path = "Path to key" end end
Once you have those lines populated with your own information, you should now be able to run
vagrant up --provider aws”
It takes a few minutes to spin up the instance. Once done you should be able to “
vagrant ssh” and use the machine. Just keep in mind that you want to terminate any unused instances, since stopping will only suspend it. A real vagrant destroy is needed to lose the ec2 resources.
Note: this box is setup with the folder sync’ feature turned off. Also, the ami’s per region are specified in the box itself, if you want to use a specific region just add a aws.region = “
You can read more about the aws provider for vagrant here : https://github.com/mitchellh/vagrant-aws
Let me know how you get on with this, if folks find it useful we can start generating these for all our vagrant images.