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 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.
Identity and access management
Follow instructions to install PE in cloud environments.
Connecting agentsCloud images contain agent packages for all supported platforms. You can install agents using any supported method.
sudo /opt/puppetlabs/cloud/bin/update_agent_repos.sh public
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.
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
puppet agent -t
puppet enterprise support
AWS – Resizing an EBS-backend
instanceNote: 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.
- Azure – Add a data disk to a VM through the Portal
Follow instructions to upgrade a standard installation.