Using Progress Chef with AWS Systems Manager
Everything You Need to Know About Chef Licensing Through AWS Marketplace
AWS Systems Manager (SSM) allows organizations to automate infrastructure configuration at scale using AWS-ApplyChefRecipes. Customers can continue using their existing AWS Systems Manager workflows while purchasing the Progress® Chef® platform through AWS Marketplace.
As part of this transition, AWS Systems Manager now supports a Chef License ID parameter within AWS-ApplyChefRecipes. Existing customers may have questions about licensing, node counting, scaling behavior and what changes are required.
This page answers the most frequently asked questions.
Getting Started
Q: What has changed?
AWS Systems Manager customers using AWS-ApplyChefRecipes can now purchase the Chef solution through AWS Marketplace and use a Chef License ID to continue downloading and running Chef Infra Client packages.
Q:Why is AWS Systems Manager introducing a Chef License ID?
The Chef License ID enables licensing validation for Chef packages obtained through AWS Marketplace while allowing customers to continue using their existing AWS Systems Manager automation workflows.
Q: What do I need to do?
To continue using AWS-ApplyChefRecipes, you should:
- Purchase Chef through AWS Marketplace
- Obtain your Chef License ID
- Add the License ID to AWS-ApplyChefRecipes
For most customers, no additional changes are required. Existing recipes, cookbooks and workflows can continue operating as before.
Understanding Chef Licensing
Q: What is considered a node?
A node is any instance where Chef Infra Client is installed or executed, including:
- Amazon EC2 instances
- Virtual machines
- Bare metal servers
Each individual instance counts as one node.
Q: How is Chef licensed?
The Chef solution uses a per-node licensing model. Every node where Chef Infra Client runs requires licensing coverage. The number of licenses required corresponds to the number of nodes being managed.
Q: How can I determine how many licenses I need?
A recommended approach is:
- Monitor where Chef runs
- Identify the peak number of unique nodes during a 24-hour period
- Purchase licenses that cover that peak usage
This helps support sufficient capacity for normal operations and scaling events.
Q: Do I need to purchase licenses upfront?
Yes. Licenses are purchased in defined quantities and can be expanded as your infrastructure grows.
Auto Scaling and Dynamic Infrastructure
Q: How does licensing work in auto-scaling environments?
For AWS Auto Scaling Groups and other dynamic environments, licensing is based on the peak number of unique instances where the Chef solution runs within a 24-hour period. Temporary instances are included if the Chef solution executes on those systems during that window.
Q: Do temporary or short-lived instances require licenses?
Yes. If Chef Infra Client runs on an instance, that instance contributes toward the peak node count used for licensing calculations.
Q: Do powered-off devices count toward licensing?
Licensing is calculated using the peak number of unique systems where the Chef solution has run within the applicable 24-hour period. If the Chef solution executed on a device during that window, it contributes to the node count.
Q: Do permanently decommissioned devices continue counting?
No. Once systems are permanently removed and fall outside the applicable measurement period, they no longer contribute to licensing calculations.
Existing Deployments and Operations
Q: What happens when I add new devices?
No re-registration or replacement of license keys is required. You simply need to support sufficient licensing coverage for the additional nodes. Existing configurations continue to operate normally.
Q: Will scaling my infrastructure cause service interruptions?
No. Scaling your environment does not require application changes or disruption of existing automation workflows, provided valid licensing coverage is maintained.
Q: What happens if I don't provide a valid License ID?
After the transition period, AWS-ApplyChefRecipes workflows will require a valid Chef License ID when downloading Chef Infra Client packages. Without a valid License ID, those workflows will no longer function as intended.
Q: Will my existing Chef automation continue to work?
Yes. Existing automation remains unchanged after adding the License ID, including:
- Cookbooks
- Recipes
- Bootstrap processes
- AWS Systems Manager Associations
- Infrastructure automation workflows
Only the License ID parameter needs to be added.
Multi-Account and Environment Questions
Q: How does licensing work across multiple AWS accounts?
Licensing is not tied to individual AWS accounts. The total number of nodes where the Chef solution runs across all AWS accounts and environments contributes toward licensing requirements.
Q: Do staging and production environments require separate licenses?
No. Licensing is not environment-specific. Nodes in staging and production both contribute toward the overall licensed node count.
Commercial Questions
Q: Can I obtain customized pricing or commercial terms?
Yes. Organizations requiring customized commercial arrangements can request a private offer from Progress by sending a request here: marketplaces@progress.com
Continue Automating with Confidence
AWS Systems Manager and Progress Chef remain a powerful combination for infrastructure automation. Whether you are managing EC2 fleets, Auto Scaling Groups, hybrid environments or configuration compliance, your existing AWS Systems Manager workflows can continue operating with minimal changes.
Ready to Get Started?
AWS Marketplace or request for a private offer.
If you would like to speak with a Chef expert, please feel free to reach out to us.
Get your Chef License ID and continue automating with the AWS Systems Manager workflows your teams already use.