---
title: "On-board new EC2 instance"
chapter: true
weight: 62
---
# On-board new EC2 instance
In this lab we're going to be using Puppet's agent mode of operation and manually accepting a request to start managing the new node.
4. Naviage to **Nodes** section via the vertical navigation bar
- You should only see a single other node currently listed, this is the PE deployment

5. Click on the **Add nodes** button
- Will send you a page which lists a couple ways of adding a node to inventory

6. Click on the **Install agents** button
- Since we're working with EC2 instances, we'll choose **Install agents**
- Puppet can also manage devices and API endpoints

7. Copy command for initiating an agent install from the cli
- To avoid setting up and distributing SSH credentials for our workshop, we'll copy the command for ***nix** under the **Install agents on the command line** section
- This command could also be integrated into your standard provisioning workflow to ensure Puppet is installed on first boot

8. Run copied command on EC2 instance
- SSH into the additional EC2 instance that you deployed during prerequisite setup as user **centos**
- Paste command onto cli

9. Run Puppet for the first time, waiting for onboarding approval
- With Puppet installed, initiate the first configuration run
- Puppet will wait for you to approve the new node, checking to see if it can continue every 5 seconds
- `sudo -i puppet agent -t --waitforcert 5`

10. Navigate to **Certificates** section of PE console
- Return to the PE console and refresh your browser
- There is now bee the number 1 next to **Certificates** in the vertical navigation bar

11. Select **Unsigned Certificates** tab
- This number 1 will also be present next to **Unsigned Certificates**
- Click on this tab

12. Accept new agent certificate
- Click on the **Accept** button

13. Wait for Puppet to finish its initial run
- Return to your SSH session and the Puppet run will have started
- When it finishes you'll likely see events related to **Sudo::Conf**
