AWS OpsWorks for Chef Automate provides a fully managed Chef Automate server and suite of automation tools that give you workflow automation for continuous deployment, automated testing for compliance and security, and a user interface that gives you visibility into your nodes and their status. Please see Configuring WSUS Email Notification to Work With Office365, How to setup and configure Windows server update services (WSUS), Important Areas to Master on WSUS (Installed and not applicable, Install 1/4, and Installed / Not applicable 100)..
Provision a Chef Automate Server in AWS. Follow this link https://aws.amazon.com/opsworks/chefautomate/ and ‘click on get Started with OpsWorks for Chef Automate’
Consequently, When setup is complete, ensure you download the Sign-in credential for the Chef Server, as AWS OpsWork does not save this for Chef Automate and cannot be downloaded afterward or viewed.
StarterKit: Download and Unzip the Starter Kit. Similarly, The Starter Kit contains a README file with examples and a knife.rb configuration file, and a private key for the primary or pivotal user.
Note: A new key pair is generated—and the old key is reset each time you download the Starter Kit.
The Starter Kit .zip file includes a simple example of a Chef repository that works with any AWS OpsWorks for Chef Automate Server. Furthermore, In the Chef repository, you store cookbooks, roles, configuration files, and other artifacts for managing your nodes with Chef. However, You should store this repository in a version control system, such as Git or AWSCodeCommit, and treat it as source code.
Note: Moreover, Never share the Starter Kit private key. If other users will be managing the Chef server, add them as administrators in the Chef Automate dashboard.
Chef Development Kit: Nonetheless, Download and run on the computer that will administer the Chef Server and Nodes. The knife utility is also part of the Chef DK.
https://docs.aws.amazon.com/opsworks/latest/userguide/welcome_opscm.html
