AWS OpsWorks Deprecation: How to Keep Managing Servers After AWS OpsWorks EOL
AWS OpsWorks deprecation happened on March 31, 2024, and AWS OpsWorks is no longer accepting new users.
Existing users of AWS OpsWorks for Puppet are encouraged to migrate Puppet servers directly to Puppet Enterprise, Open Source Puppet, or Amazon Elastic Compute Cloud (Amazon EC2). Read on for more information on your options.
AWS OpsWorks Deprecation & What It Means for Your AWS Infrastructure
Amazon Web Services (AWS) stopped accepting new customers for AWS OpsWorks Stacks in early 2024. AWS OpsWorks deprecation discontinued the use of the OpsWorks console, API, CLI, and CloudFormation resources.
AWS OpsWorks used to provide managed instances of Puppet and Chef. It helped customers migrate to the cloud and automate server configuration, deployment, and management across Amazon EC2 instances or on-premises environments using Puppet and Chef.
AWS OpsWorks reached end of life (EOL) in early 2024 and is no longer accepting new customers. Existing customers are no longer able to use the OpsWorks console, API, CLI, or CloudFormation resources as of May 26, 2024.
In the wake of the AWS OpsWorks deprecation, customers must choose alternative options for configuring and managing their applications in AWS.
Back to topWhat to Do After AWS OpsWorks Deprecation for Puppet Enterprise
If you’re using AWS OpsWorks and would like to continue managing servers and other resources managed by Puppet, you should migrate to either Open Source Puppet or Puppet Enterprise.
Both options let you continue using Puppet code to maintain the AWS infrastructure you created and deployed with AWS OpsWorks for Puppet Enterprise. (Read on for a quick comparison.)
If you’re not ready to tackle migration on your own, or if you don’t have a Puppet pro on staff, Puppet Professional Services is your go-to for choosing the best path forward after AWS OpsWorks for Puppet Enterprise is discontinued. The Professional Services team can help you choose between Open Source Puppet and Puppet Enterprise, determine the scope of your migration, and provide support every step of the way.
Why Migrate to Puppet Enterprise from AWS OpsWorks?
As mentioned, both Open Source Puppet and Puppet Enterprise offer the same powerful Puppet codebase for managing infrastructure, wherever you’re deployed. Both options also offer thousands of modules available via the Puppet Forge (including many Puppet-supported modules) and access to the vibrant, welcoming Puppet Community.
When deciding between Open Source Puppet and Puppet Enterprise, it’s worth considering the differences. Puppet's open source version is the free, openly available offering of Puppet that provides a starting point for managing infrastructure on your own. Open Source Puppet offers a command-line interface (CLI) instead of the graphical user interface (GUI) found in Puppet Enterprise, and lacks several of the controls, feedback loops, and reporting options offered in the commercial version.
Puppet Enterprise customers get the same powerful automation and configuration management tools found in Open Source Puppet, plus additional features and benefits that save time, empower your team, and make managing complex infrastructure a lot easier.
Puppet Enterprise includes…
- A graphical user interface, role-based access control (RBAC), and other features that enhance functionality and usability.
- Instant access to the latest version of Puppet Enterprise: AWS OpsWorks was typically at least one or two versions behind the current version of Puppet Enterprise. When you start managing infrastructure directly through Puppet Enterprise, you get access to the latest security updates and features that come with each new version.
- Priority Support: Puppet Enterprise users get priority placement for Support as well as 24/7 Support options. Shorter wait times means more uptime and fewer headaches.
Back to topNeed more info to decide between Puppet's open source and Enterprise versions? Get the free guide to Open Source Puppet vs. Puppet Enterprise.
[Original Post] Announcing AWS OpsWorks for Puppet Enterprise
The following article was originally published in 2017. Portions have been maintained for contextual purposes after the deprecation of AWS OpsWorks for Puppet Enterprise.
Amazon Web Services recently announced AWS OpsWorks for Puppet Enterprise. But what does that mean for Puppet Enterprise users? Let's explore how this enhancement can help support your move into the cloud.
Back to topWhat is AWS OpsWorks?
AWS OpsWorks is a cloud-based configuration management service that enables enterprises to automate the management of their cloud infrastructure running on AWS.
OpsWorks has seen a lot of demand for a Puppet Enterprise offering and we’ve been working closely with the OpsWorks team to meet that demand.
With OpsWorks for Puppet Enterprise, you can use the same configurations to manage both your on-premises and cloud infrastructure, accelerating migration to the cloud and increasing your ability to efficiently scale your operations in a hybrid environment.
AWS OpsWorks for Puppet Enterprise is a fully managed service hosted on AWS. All you need is an AWS account, and with just a couple of clicks, you can have Puppet Enterprise up and running on AWS in under 10 minutes.
Back to topBenefits of AWS OpsWorks + Puppet Enterprise
Note: AWS OpsWorks for Puppet Enterprise went EOL after March 31, 2024. Users of the integration will be unable to manage Puppet servers using the OpsWorks console or API, and will have to migrate to Open Source Puppet or Puppet Enterprise to continue managing their Puppet infrastructure.
- OpsWorks automatically handles software updates to the Puppet Enterprise server.
- You can specify maintenance windows for routine maintenance.
- Backup and restore capabilities give you the flexibility to migrate Puppet servers across virtual machines so recovery from outages is automatic.
- Managing your Puppet Enterprise server is easy through the Puppet Enterprise console (GUI), AWS Management Console, and the AWS Command Line Interface (CLI).
- Flexible consumption-based hourly billing.
- Workflows tailored to the cloud make it easy to bring your cloud resources under management. Register nodes without signing certificate signing requests on the Puppet server. The connection to the module code repository is established as part of the provisioning process. And, if you don't have an existing code repo, we provide an AWS-managed source control repository to securely store your infrastructure code.
Your Learning Checklist:
- Get the free ebook Simplify AWS Automation with Puppet
- Learn more about how Puppet integrates with AWS
This blog was originally published on November 15, 2017, and has since been updated for accuracy and relevance.
Back to top