Featured resource
Tech Upskilling Playbook 2025
Tech Upskilling Playbook

Build future-ready tech teams and hit key business milestones with seven proven plays from industry leaders.

Learn more
  • Labs icon Lab
  • Cloud
Google Cloud Platform icon
Labs

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).**

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 45m
Last updated
Clock icon May 06, 2025

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Create the Client Key

    1. Move into the working directory for our Packer build.
    2. Generate a new client key called packer, and output the key to the working directory.
    3. There's no need to change the provided configuration. Save and exit to finish.
  2. Challenge

    Add the Provisioner

    1. Open the provided packer.json file.
    2. Since the chef-client provisioner installs Chef for us, there's minimal pre-configuration we need to preform in the provided shell provisioner block. That said, we do need to ensure we can access our Chef Infra Server at chef.ec2.internal.
    3. We also need to move the packer.pem file we just created to the remote machine; to do this, we want to use the file provisioner. 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 shell provisioner for this.
    4. Additionally, we want to make sure the certs supplied in ~/chef-repo/.chef/trusted_certs are added to the remote.
    5. We can now add our chef-client block. 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.
  3. Challenge

    Test the Build

    1. Update the file with the provided access key, secret key, and subnet ID.
    2. Save and exit the file.
    3. Test the build.

Pluralsight Skills gives leaders confidence they have the skills needed to execute technology strategy. Technology teams can benchmark expertise across roles, speed up release cycles and build reliable, secure products. By leveraging our expert content, skill assessments and one-of-a-kind analytics, keep up with the pace of change, put the right people on the right projects and boost productivity. It's the most effective path to developing tech skills at scale.

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.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.