Menu
AWS OpsWorks
User Guide (API Version 2013-02-18)

AWS OpsWorks for Chef Automate

AWS OpsWorks for Chef Automate lets you run a Chef Automate server in AWS. You can provision a Chef server within minutes, and let AWS OpsWorks Stacks handle its operations, backups, restorations, and software upgrades. AWS OpsWorks for Chef Automate frees you to focus on core configuration management tasks, instead of managing a Chef server.

A Chef Automate server manages the configuration of nodes in your environment by instructing chef-client which Chef recipes to run on the nodes, stores information about nodes, and serves as a central repository for your Chef cookbooks. AWS OpsWorks for Chef Automate provides Chef servers and premium features of Chef Automate: visibility, workflow, and compliance.

An AWS OpsWorks for Chef Automate server runs on an Amazon Elastic Compute Cloud instance. The instance is configured to run the newest version of Amazon Linux (2016.09), Chef Server 12.x, and the most current version of Chef Automate Server, version 0.6.x.

You can connect any on-premises computer or EC2 instance that is running a supported operating system and has network access to an AWS OpsWorks for Chef Automate server. For a list of supported operating systems for nodes that you want to manage, see the Chef website. The chef-client agent software is installed on nodes that you want to manage with a Chef server.

Region Support for AWS OpsWorks for Chef Automate

The following regional endpoints support AWS OpsWorks for Chef Automate servers. AWS OpsWorks for Chef Automate creates resources that are associated with your Chef servers, such as instance profiles, IAM users, and service roles, in the same regional endpoint as your Chef server. Your Chef server must be in a VPC in the same region. You can use a VPC that you create or already have, or use the default VPC.

  • US East (N. Virginia) Region

  • US West (Oregon) Region

  • EU (Ireland) Region