This is the demo repository for my upcoming 2016 AWS Advent article about Terraform modules. It is a continuation of my previous article and repository found at the following locations:
- https://github.com/vancluever/packer-terraform-example
- https://vancluevertech.com/2016/02/02/aws-world-detour-packer-and-terraform/
- A small ruby gem (
vancluever_hello
). This is built via rubygems tasks usingrake
. - A Chef recipe designed for deploying the application (
packer_payload
). This is a single-purpose cookbook that is not intended to be shared in Supermarket, etc. It's only intended for use with Packer. With that said, having a cookbook allows you to port this functionality to a general-use cookbook if necessary - this can then be included from a freshpacker_payload
cookbook. - A packer template located at
packer/ami.json
. - Three Terraform examples:
- The first one in the root
terraform/
directory is the main subject of the article. - Secondary examples exist in subdirectories of this one:
terraform/multi_asg
sets up 2 unique ASGs,terraform/with_ssl
sets up the ASG with a SSL ALB. You need an IAM or ACM certificite and a Route 53 hosted zone to run this example.
The project uses 4 Terraform modules:
The Rakefile
has tasks for managing the full lifecycle from building of the
gem, to AMI, to deployment. The list is below:
rake ami # Create an application AMI with Packer
rake berks_cookbooks # Vendors dependent cookbooks in berks-cookbooks (for Packer)
rake build # Build vancluever_hello-0.1.1.gem into the pkg directory
rake clean # Remove any temporary products
rake clobber # Remove any generated files
rake infrastructure # Deploy infrastructure using Terraform
rake kitchen # Run test-kitchen on packer_payload cookbook
rake tf_modules # Gets Terraform modules
In addition to that, the file also has helper functions for looking up AMI IDs to be used in the build process.
To prepare the repository for use, clone it and run
bundle install --binstubs --path vendor/bundle
You should then be good to start using bundle exec rake
. Get a list of
commands by running bundle exec rake -T
.
You also need Packer and Terraform.
Finally, valid AWS credentials will need to be available in your credential
chain, either as environment variables (ie: AWS_ACCESS_KEY
,
AWS_SECRET_ACCESS_KEY
and AWS_SESSION_TOKEN
), or your credentials in your
~/.aws
directory.
You can also control the build process through the following environment variables:
DISTRO
To control the Ubuntu distribution to use (defaulttrusty
).REGION
To control the region to deploy to (defaultus-east-1
).TF_CMD
To control the Terrafrom command (defaultapply
. Change this todestroy
to tear down the infrastructure).TF_DIR
To control the Terrafrom directory (defaultterraform
, you would change this toterraform/multi_asg
orterraform/with_ssl
if you wanted to try the other examples).
Copyright 2016 Chris Marchesi
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.