Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
Restore an OpsWorks for Puppet Enterprise Server from a Backup - AWS OpsWorks

Restore an OpsWorks for Puppet Enterprise Server from a Backup

PDFRSS
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 or through AWS Premium Support.

After browsing through your available backups, you can easily choose a point in time from which to restore your OpsWorks for Puppet Enterprise server. Server backups contain configuration-management software persistent data such as modules, classes, node associations, database information (including reports, facts, etc.). Performing an in-place restoration of a server (that is, restoring the existing OpsWorks for Puppet Enterprise server to a new EC2 instance) reregisters nodes that were registered at the time of the backup that you use to restore the server, and switches traffic to the new instance if restoration is successful, and the restored OpsWorks for Puppet Enterprise server state is Healthy. Restoring to a newly-created OpsWorks for Puppet Enterprise server does not maintain node connections. Restoring a server does not update the version of Puppet software; it applies the same Puppet versions and configuration-management data that are available in the backup that you choose.

Restoring a server typically takes more time than creating a new server; the time depends on the size of the backup you choose. After restoration is complete, the old EC2 instance remains in a Running or Stopped state, but only temporarily. It is eventually terminated.

In this release, you can use the AWS CLI to restore a Puppet master in OpsWorks for Puppet Enterprise.

Note

You can also run the restore-server command to change the current instance type, or to restore or set your SSH key if it is lost or compromised.

To restore a server from a backup

  1. In the AWS CLI, run the following command to return a list of available backups and their IDs. Make a note of the ID of the backup that you want to use. Backup IDs are in the format myServerName-yyyyMMddHHmmssSSS.

    aws opsworks-cm --region region name describe-backups

  2. Run the following command.

    aws opsworks-cm --region region name restore-server --backup-id "myServerName-yyyyMMddHHmmssSSS" --instance-type "Type of instance" --key-pair "name of your EC2 key pair" --server-name "name of Puppet master"

    The following is an example.

    aws opsworks-cm --region us-west-2 restore-server --backup-id "MyPuppetServer-20161120122143125" --server-name "MyPuppetServer"

  3. Wait until restoration is complete.

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.