Installing PE in cloud environments

To install cloud PE, launch a marketplace image from your chosen cloud provider.

Launch an AWS image

You can launch a cloud PE image from the AWS console or any available AWS SDKs or third-party tools.

  1. Launch a PE image and specify details for your deployment.
    • EC2 instance type – The image size used for your deployment. For recommendations, see Hardware requirements for standard installations.

    • EC2 VPC and subnet – The VPC or subnet in which to deploy your image.

    • EC2 security group – The security group policy to use for your deployment.

    To control access to the image, a new key pair is created.
  2. Connect to the image using your new key pair and the username puppetadmin:
    ssh -i ~/.ssh/<KEYPAIR_PRIVATE>.pem puppetadmin@<PRIMARY_HOSTNAME>
    SSH keys are automatically provisioned, and no password is required.
  3. Wait for the image to boot and for PE configuration to complete.
    To track progress, run the check_status.sh script:
    sudo /opt/puppetlabs/cloud/bin/check_status.sh --wait
  4. Specify a console admin password:
    sudo /opt/puppetlabs/puppet/bin/puppet infrastructure console_password

    Console access is disabled until the password is set.

  5. Using a web browser, connect to the console at https://<PRIMARY_HOSTNAME>, accept the console's certificate, and login with the username admin and the password you specified during installation.
    Tip: The console uses an SSL certificate created by your own local Puppet certificate authority. Because this authority is specific to your site, web browsers don't know it or trust it, and you must add a security exception in order to access the console.
    The console indicates that your primary server is actively managed by showing 1 Nodes run in enforcement.
Results
Your primary server is now ready to manage nodes.

Launch an Azure image

You can launch a cloud PE image from the Azure Portal, Powershell, or SDKs from Ruby, Python, Go, or Java.

  1. Launch a PE image and specify details for your deployment.
    • Resource Group – Creates a new resource group or reuses an existing group.

    • Location – The location for the resource group. If you use an existing resource group, the location must match the resource group's location.

    • Admin Password – The password for the admin user. If you select SSH authentication, the password you specify is used as a backup authentication method.

    • VM Size – The size used for your deployment. For recommendations, see Hardware requirements for standard installations.

    • Admin User Name – The username to use when logging in with SSH.

    • Authentication TypesshPublicKey or password

    • SSH Public Key – Your SSH public key, if you select SSH as your authentication type.

    • Virtual Network New Or Existing – Creates a new virtual network or uses an existing network. If you select existing, you don't need to enter an address prefix or subnet.

    • Public IP Address New Or Existingnew to specify a static IP address. If the IP is dynamic and the VM is restarted, you won't be able to access the console, because the console uses the initial public IP address.

    • Public IP Address Domain Name Label – The prefix of the VM's fully qualified domain name.

    • Storage Account New Or Existing – Creates a new storage account or uses an existing account. If you select existing, you don't need to enter an account type.

    To control access to the image, a new key pair is created.
  2. Connect to the image using your new key pair and the username puppetadmin:
    ssh -i ~/.ssh/<KEYPAIR_PRIVATE>.pem puppetadmin@<PRIMARY_HOSTNAME>
    SSH keys are automatically provisioned, and no password is required.
  3. Wait for the image to boot and for PE configuration to complete.
    To track progress, run the check_status.sh script:
    sudo /opt/puppetlabs/cloud/bin/check_status.sh --wait
  4. Specify a console admin password:
    sudo /opt/puppetlabs/puppet/bin/puppet infrastructure console_password

    Console access is disabled until the password is set.

  5. Using a web browser, connect to the console at https://<PRIMARY_HOSTNAME>, accept the console's certificate, and login with the username admin and the password you specified during installation.
    Tip: The console uses an SSL certificate created by your own local Puppet certificate authority. Because this authority is specific to your site, web browsers don't know it or trust it, and you must add a security exception in order to access the console.
    The console indicates that your primary server is actively managed by showing 1 Nodes run in enforcement.
Results
Your primary server is now ready to manage nodes.

Launch an Oracle image

You can launch a cloud PE image from the Oracle Cloud Marketplace console or any available SDKs or third-party tools.

  1. Launch a PE image and specify details for your deployment.
    • Shape – The image size used for your deployment. For recommendations, see Hardware requirements for standard installations.

    • VCN – The Virtual Cloud Network or subnet in which to deploy your image.

    • Network Security Groups – The security group policy to use for your deployment. These must have all the standard ports PE requires so that services like the console and Puppet Server work correctly.

  2. Use the Oracle Cloud console to get an SSH key pair using your chosen method and save it.
  3. Connect to the image using your new key pair and the username puppetadmin:
    ssh -i ~/.ssh/<KEYPAIR_PRIVATE>.pem puppetadmin@<PRIMARY_HOSTNAME>
    SSH keys are automatically provisioned, and no password is required.
  4. Wait for the image to boot and for PE configuration to complete.
    To track progress, run the check_status.sh script:
    sudo /opt/puppetlabs/cloud/bin/check_status.sh --wait
  5. Specify a console admin password:
    sudo /opt/puppetlabs/puppet/bin/puppet infrastructure console_password

    Console access is disabled until the password is set.

  6. Using a web browser, connect to the console at https://<PRIMARY_HOSTNAME>, accept the console's certificate, and login with the username admin and the password you specified during installation.
    Tip: The console uses an SSL certificate created by your own local Puppet certificate authority. Because this authority is specific to your site, web browsers don't know it or trust it, and you must add a security exception in order to access the console.
    The console indicates that your primary server is actively managed by showing 1 Nodes run in enforcement.
Results
Your primary server is now ready to manage nodes.