Configure Puppet Control Repository

The first step in setting up a new Puppet Enterprise deployment is importing a control repository, which contains the Puppet code which is used to define the configuration of managed resources.

Before you get started ensure that Puppet Enterprise has completed its post-deployment configuration process! The steps for ensuring setup are complete are documented here on the Puppet documentation website.

Alternatively, you can connec to your EC2 instance by following these steps: EC2 Connect

  1. Navigate to the Puppet Enterprise console, which runs over the standard HTTPS port (443)

    • Find and click on Node groups, found in the left side navigation panel Step 1
  2. Expand PE Infrastructure and click on PE Master Step 2

  3. Click on Classes, found in the horizontal set of tabs Step 3

  4. Scroll down until you find Class: puppet_enterprise::profile::master

    • Use the drop down menu Parameter Name and find r10k_remote
    • Set r10k_remote to and click Add to node group
    • Now set code_manager_auto_configure to true
    • Commit changes by clicking on Commit 2 changes Step 4
  5. Log into your PE deployment as puppetadmin via SSH and run Puppet via the CLI

    • sudo -i puppet agent -t Step 5
  6. Once you see similar output and you’re returned to a command prompt then continue to the next step Step 6

  7. To deploy our Control Repository we first authenticate to the PE API

    • sudo -i puppet access login --lifetime=1y
    • Login with credentials set during the AWS Marketplace PE deployment process Step 7
  8. Deploy the production code environment

    • sudo -i puppet code deploy production --wait Step 8