Cloud PE

Puppet Enterprise 2019.8 cloud images are available from several providers.

Cloud images contain a standard installation with PE services running on a primary server installed in your chosen cloud environment. You can use cloud images to manage deployments up to 2,500 nodes. Cloud deployments beyond 2,500 nodes aren't recommended because cloud PE doesn't support compilers.

After launching a cloud image, you can use PE just as you would any on-premises standard installation.

Use these tips and links as you work with your cloud deployment.

Cloud providers

PE cloud images are available from these providers:


Cloud images follow a bring-your-own-license (BYOL) model, so you can use any existing PE license with your chosen cloud provider. With AWS, you may also purchase licenses directly from the AWS Marketplace using Enterprise Discount Program (EDP) credits. View AWS pricing information for details.

System requirements

Follow hardware requirements for cloud deployments.

Security groups

Follow firewall requirements for standard installations. See a sample security group policy in EC2-style JSON here.

Identity and access management

For AWS, follow Identity and Access Management (IAM) best practices to create the deployment user and role:


Follow instructions to install PE in cloud environments.

Connecting agents

Cloud images contain agent packages for all supported platforms. You can install agents using any supported method.
To manage nodes outside of your cloud provider, or across cloud deployments, configure your primary server by running the script:
sudo /opt/puppetlabs/cloud/bin/ public

Configuring DNS

In cloud deployments, PE uses the primary server's private hostname to generate certificates, and includes the public hostname and puppet as alternate DNS names.

Managing nodes by their private hostname retains consistency when nodes are resized or changed to a different image type.


PE cloud images are tuned using default settings for standard installations. You can tune your primary server in cloud deployments as you would any on-premises installation.

Running commands on nodes

When running these commands on nodes in Azure environments, you must first switch to the superuser role by running sudo su.
  • puppet agent -t

  • puppet enterprise support

  • puppet infrastructure

  • puppet license

  • puppet lookup

  • puppet node

  • puppet plugin

  • puppetserver ca


As your infrastructure grows, moving to a larger cloud instance or VM can improve system performance. Follow instructions from your cloud provider to scale your deployment.
  • AWSResizing an EBS-backend instance
    Note: During EC2 resizing, your instance's public hostname and IP address might change. To access the PE console, connect to the new public hostname. Resizing the instance doesn't change the private hostname or IP address, and therefore no change is required for PE services or managed nodes.
  • AzureAdd a data disk to a VM through the Portal


Follow instructions to upgrade a standard installation.


Find tips on troubleshooting cloud deployments.