summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFranck Cuny <franck.cuny@gmail.com>2014-02-01 17:07:00 -0800
committerFranck Cuny <franck.cuny@gmail.com>2014-02-01 17:07:00 -0800
commit6299f101db09dd096ab41a4f58fef791263b2236 (patch)
tree561864dc1b4cc4bb4613b1eaaacb9780aa113b17
parentAdd picture for the ansible/vagrant/ec2 article. (diff)
downloadlumberjaph-6299f101db09dd096ab41a4f58fef791263b2236.tar.gz
Insert a picture.
-rw-r--r--_posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/_posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md b/_posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
index 25483cb..5ccb624 100644
--- a/_posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
+++ b/_posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
@@ -81,6 +81,14 @@ default : ok=2 changed=1 unreachable=0 failed=0
As we can see, everything went well, and the application `htop` was successfully installed. We can now run `vagrant ssh` and once logged inside the VM, run `htop`.
+</section>
+
+<figure>
+<img alt="provisioning" src="/static/imgs/vagrant-ansible-ec2.jpg" Width="100%" height="100%" class='portrait' align='center'>
+</figure>
+
+<section>
+
## AWS
I've created a key pair for Vagrant in the AWS console. Note the access and secret access keys, and download the SSH private key too. For this article, we will put the key into the same directory as our playbook and Vagrant's configuration.