- A Cloud Guru
Provisioning a Packer Image with chef-client
Packer lets us create machine images for a variety of platforms through code. Part of the image creation process involves provisioning the machine, which can be done with a variety of provisioners, including Chef. Packer is even able to connect to an existing Chef Infra Server and use the cookbooks there to provision the resulting image. In this lab, we'll do just that to set up a web server image that hosts our company's website. **Note: You will find the AWS Access Key, Secret Access Key and the subnet ID required for the Packer configuration within the 'Credentials' tab (use the arrow button to see any hidden servers).**
Table of Contents
Create the Client Key
- Move into the working directory for our Packer build.
- Generate a new client key called
packer, and output the key to the working directory.
- There's no need to change the provided configuration. Save and exit to finish.
Add the Provisioner
- Open the provided
- Since the
chef-clientprovisioner installs Chef for us, there's minimal pre-configuration we need to preform in the provided
shellprovisioner block. That said, we do need to ensure we can access our Chef Infra Server at
- We also need to move the
packer.pemfile we just created to the remote machine; to do this, we want to use the
fileprovisioner. When working with
chef-client, Packer uses the directory
/tmp/packer-chef-client. For ease, we'll store our key here. However, note that this directory has yet to be created. We'll need to update our
shellprovisioner for this.
- Additionally, we want to make sure the certs supplied in
~/chef-repo/.chef/trusted_certsare added to the remote.
- We can now add our
chef-clientblock. We'll want to define our server URL, the validation client name and key path, as well as the location of our trusted certs and client key. Finally, we'll want to supply the name of the node (
packer) and the desired run list.
- Open the provided
Test the Build
- Update the file with the provided access key, secret key, and subnet ID.
- Save and exit the file.
- Test the build.
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.