AWS OpsWorks for Chef Automate End of Life FAQs
Important
AWS OpsWorks for Chef Automate is no longer accepting new customers. Existing customers will be unaffected until May 5, 2024 at which time the service will become unavailable. We recommend that existing customers migrate to Chef SaaS or an alternative solution.
Topics
- How will existing users be affected by this End of Life?
- What happens to my servers if I don’t take any action?
- What alternatives can I transition to?
- Is the service still accepting new customers?
- Will the End of Life affect all AWS Regions at the same time?
- What level of technical support is available?
- I am a current customer of OpsWorks for Chef Automate and I need to launch a server in an account which was not using the service previously. Am I able to do this?
- Will there be any major feature releases over the next year?
How will existing users be affected by this End of Life?
Existing customers will be unaffected until May 5, 2024, the End of Life date for OpsWorks for Chef Automate. After the End of Life date, customers will no longer be able to manage their servers using the OpsWorks console or API.
What happens to my servers if I don’t take any action?
Starting May 5, 2024, you will no longer be able to manage your servers using the OpsWorks console or API.
At that time, we will stop performing any ongoing management functions for your servers such as backups or maintenance.
To limit the impact to customers, we will leave any EC2 instances running that are backing up Chef Automate servers, but
their licenses will no longer be valid as usage is no longer covered (or billed for) under the OpsWorks for Chef Automate
service agreement with Chef. You will need to contact Chef
What alternatives can I transition to?
AWS and Progress Chef recommend you migrate to their new Chef SaaS offering so
that you can continue to benefit from a fully-managed Chef Automate service.
To get started with Chef SaaS, you can contact Chef
If Chef SaaS will not meet your needs because you prefer to run Chef Automate
on EC2 instances in AWS accounts you control, Chef provides multiple options
including an AWS Marketplace Bring Your Own License (BYOL) model
Is the service still accepting new customers?
No. AWS OpsWorks for Chef Automate is no longer accepting new customers and only existing customers are able to launch new servers at this time.
Will the End of Life affect all AWS Regions at the same time?
Yes. The API and Console will reach End of Life and be unusable as of May 5, 2024 in all AWS Regions.
For information about the AWS Regions where AWS OpsWorks for Chef Automate is available, see AWS Regional Services List
What level of technical support is available?
AWS will continue to provide the same level of support for OpsWorks for Chef Automate
that customers have today up until the End of Life date. If you have questions or concerns,
you can contact the AWS Support Team on AWS re:Post
I am a current customer of OpsWorks for Chef Automate and I need to launch a server in an account which was not using the service previously. Am I able to do this?
Generally not, unless there are exceptional circumstances to do so. If you have a special situation, reach out to the AWS Support Team on AWS re:Post
Will there be any major feature releases over the next year?
No. As the service is reaching End of Life, we will not release any new features. However, we will continue to make security improvements and manage servers as expected until the End of Life date.
