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.