Getting Started with OpsWorks for Puppet Enterprise
Important
The AWS OpsWorks for Puppet Enterprise service reached end of life on March 31, 2024 and has been disabled for both new and existing customers. We strongly recommend customers migrate
their workloads to other solutions as soon as possible. If you have questions about migration, reach out to the AWS Support Team on AWS re:Post
OpsWorks for Puppet Enterprise lets you run a Puppet Enterprise
Starting May 3, 2021, OpsWorks for Puppet Enterprise stores some Puppet Enterprise server attributes in AWS Secrets Manager. For more information, see Integration with AWS Secrets Manager.
The following walkthrough helps you create your first Puppet master in OpsWorks for Puppet Enterprise.
Prerequisites
Before you begin, you must complete the following prerequisites.
Topics
Install the Puppet Development Kit
-
From the Puppet website, download the Puppet Development Kit
that matches your local computer's operating system. -
Install the Puppet Development Kit.
-
Add the Puppet Development Kit to your local computer's
PATH
variable.-
On a Linux or macOS operating system, you can add the Puppet Development Kit to your
PATH
variable by running the following command in a Bash shell.echo 'export PATH=/opt/puppetlabs/pdk/bin/pdk:$PATH' >> ~/.bash_profile && source ~/.bash_profile
-
On a Windows-based operating system, you can add the Puppet Development Kit to your
PATH
variable by using the following .NET Framework command in a PowerShell session, or in the Environment Variables dialog box accessible from System Properties. You may need to run your PowerShell session as an administrator to run the following command.[Environment]::SetEnvironmentVariable("Path","
new path value
","Machine")
-
Install the Puppet Enterprise Client Tools
Puppet Enterprise (PE) client tools are a set of command-line tools that let you
access Puppet Enterprise services from your workstation. The tools can be installed on
many different operating systems, and they can also be installed on nodes that you are
managing by using Puppet. For information about supported operating systems for the
tools, and how to install them, see Installing PE client tools
Set Up a Git Control Repository
Before you can launch a Puppet master, you must have a control repository configured
in Git to store and change-manage your Puppet modules and classes. A URL to a Git
repository and HTTPS or SSH account information to access the repository are required in
the steps to launch your Puppet Enterprise master server. For more information about how
to set up a control repository that your Puppet Enterprise master will use, see Setting up
a control repositorycontrol-repo
sample repository on GitHub
├── LICENSE ├── Puppetfile ├── README.md ├── environment.conf ├── hieradata │ ├── common.yaml │ └── nodes │ └── example-node.yaml ├── manifests │ └── site.pp ├── scripts │ ├── code_manager_config_version.rb │ ├── config_version.rb │ └── config_version.sh └── site ├── profile │ └── manifests │ ├── base.pp │ └── example.pp └── role └── manifests ├── database_server.pp ├── example.pp └── webserver.pp
Setting up a repository by using CodeCommit
You can create a new repository by using CodeCommit. For more information about how to
use CodeCommit to create your control repository, see Optional: Use AWS CodeCommit as a Puppet r10k Remote
Control Repository in this guide. For more information about how
to get started with Git on CodeCommit, see Getting
started with AWS CodeCommit. To authorize your OpsWorks for Puppet Enterprise server for your
repository, attach the AWSCodeCommitReadOnly
policy to your IAM instance
profile role.
Set Up a VPC
Your OpsWorks for Puppet Enterprise master must operate in an Amazon Virtual Private Cloud. You can add it to an existing VPC, use the default VPC, or create a new VPC to contain the server. For information about Amazon VPC and how to create a new VPC, see the Amazon VPC Getting Started Guide.
If you create your own VPC, or use an existing one, the VPC should have the following settings or properties.
-
The VPC should have at least one subnet.
If your OpsWorks for Puppet Enterprise master will be publicly accessible, make the subnet public, and enable Auto-assign public IP.
-
DNS resolution should be enabled.
-
On the subnet, enable Auto-assign public IP.
If you are unfamiliar with creating VPCs or running your instances in them, you can
run the following AWS CLI command to create a VPC with a single public subnet, by using an
AWS CloudFormation template that AWS OpsWorks provides for you. If you prefer to use the AWS Management Console, you can
also upload the template
aws cloudformation create-stack --stack-name OpsWorksVPC --template-url https://s3.amazonaws.com/opsworks-cm-us-east-1-prod-default-assets/misc/opsworks-cm-vpc.yaml
Set Up an EC2 Key Pair (Optional)
An SSH connection is not necessary or recommended for typical management of the Puppet server; you can use the AWS Management Console and AWS CLI commands to perform many management tasks on your Puppet server.
An EC2 key pair is required to connect to your server by using SSH in the event that you lose or want to change the sign-in password for the Puppet Enterprise web-based console. You can use an existing key pair, or create a new key pair. For more information about how to create a new EC2 key pair, see Amazon EC2 Key Pairs.
If you don't need an EC2 key pair, you are ready to create a Puppet Enterprise master.
Prerequisites for Using a Custom Domain (Optional)
You can set up your Puppet Enterprise master on your own domain, specifying a public endpoint in a custom domain to use as the endpoint of your server. When you use a custom domain, all of the following are required, as described in detail in this section.
Set Up a Custom Domain
To run your Puppet Enterprise master on your own custom domain, you will need a
public endpoint of a server, such as https://aws.my-company.com
. If you
specify a custom domain, you must also provide a certificate and a private key, as
described in the preceding sections.
To access the server after you create it, add a CNAME DNS record in your preferred
DNS service. This record must point the custom domain to the endpoint (the value of
the server's Endpoint
attribute) that is generated by the Puppet master
creation process. You cannot access the server by using the generated
Endpoint
value if the server is using a custom domain.
Get a Certificate
To set up your Puppet master on your own custom domain, you need A PEM-formatted HTTPS certificate. This can be be a single, self-signed certificate, or a certificate chain. As you complete the Create a Puppet Enterprise Master workflow, if you specify this certificate, you must also provide a custom domain and a private key.
The following are requirements for the certificate value:
-
You can provide either a self-signed, custom certificate, or the full certificate chain.
-
The certificate must be a valid X509 certificate, or a certificate chain in PEM format.
-
The certificate must be valid at the time of upload. A certificate can't be used before its validity period begins (the certificate's
NotBefore
date), or after it expires (the certificate'sNotAfter
date). -
The certificate’s common name or subject alternative names (SANs), if present, must match the custom domain value.
-
The certificate must match the value of the Custom private key field.
Get a Private Key
To set up your Puppet master on your own custom domain, you need a private key in PEM format for connecting to the server by using HTTPS. The private key must not be encrypted; it cannot be protected by a password or passphrase. If you specify a custom private key, you must also provide a custom domain and a certificate.