Amazon Web Services (AWS) Integration

Accelerate Migration to AWS Cloud with Puppet

Unlock the full value that Amazon Web Services (AWS) can deliver to your organization — and manage it with greater agility, more efficiency, and the flexibility to scale when you need to. Whether you’re migrating workloads to AWS Cloud or starting a greenfield project, Puppet can help you ensure consistency across your on-premises and cloud infrastructure and keep it compliant.

Manage cloud infrastructure at scale

It’s easy to spin up new instances in AWS, but it’s a lot harder to ensure they’re always configured correctly. Puppet Enterprise lets you define your infrastructure as code, which gives you a consistent and repeatable way to provision, configure, and manage your AWS infrastructure. This allows you to scale quickly during peak times and minimizes the risk of downtime due to unauthorized changes. With Puppet Enterprise, small teams can effectively manage thousands of instances without increasing headcount.

GET EBOOK

The Free Guide to Cloud Scalability + Efficiency Operating across clouds, data centers, and on-premises? Download our guide on how to avoid unnecessary inefficiencies when scaling up and out.

Smooth migrations

Customers can choose to rehost or replatform applications to the cloud with Puppet Enterprise without needing to re-architect around a new automation solution. The existing installation documentation and best practices provided by Puppet to deploy PE includes reference architectures that are intentionally agnostic, implementing similar concepts of load balancing, disaster recovery, and network segmentation that are adaptable to AWS native services.

The most common recommendation for cloud deployments of Puppet Enterprise which will ensure performance and resilient installation is to segment your PE deployment by region. This is true for each reference architecture found within the Puppet Enterprise documentation.

Inside each individual region an installation’s primary and optional secondary services will often be split across multiple availability zones, while additional compilers can reside behind a Network Load Balancing to enable an elastic pool of resources that ensures Puppet Enterprise can support on demand workloads. For a greater level of control over direct access by humans and infrastructure, PE should live within its own highly scrutinized security zone and VPC.

The following diagram is an example of adapting the Large PE reference architecture for AWS. Depending on your organization’s scaling requirements it might make more sense to deploy a Standard or Extra Large architecture, both architectures are adaptable in a similar manner.

Puppet Enterprise Large Architecture deployed on AWS

Puppet Enterprise in AWS Marketplace

It’s easy to find and launch Puppet Enterprise directly from the AWS Marketplace. You can bring your own licenses to the AWS cloud and deploy Puppet Enterprise using our AMI available in AWS Marketplace. For instructions on how to launch the AMI, see our Amazon Web Services Marketplace Image User Guide.

To make it easy to get started, the AMI:

• Comes with Puppet pre-installed and it is automatically and securely configured while booting your EC2 instance.
• Includes scripts to automate common tasks and configure PE to manage nodes wherever they live — on-premises, offsite data centers, EC2, or other cloud providers.

The Puppet Enterprise AMI is the fastest and easiest way to adopt automation for your cloud projects from the get-go without committing to a long-term contract.

AWS OpsWorks for Puppet Enterprise

AWS OpsWorks for Puppet Enterprise became unavailable after March 31, 2024, and is no longer accepting new users.

Existing users are encouraged to migrate Puppet servers from OpsWorks to Puppet Enterprise, Open Source Puppet, or Amazon Elastic Compute Cloud (Amazon EC2).

For more information on your migration options and how to keep managing your AWS infrastructure with Puppet, read our blog on AWS OpsWorks for Puppet Enterprise EOL.