The Chef-Client agent runs Chef recipes on both physical and virtual servers, often called nodes or instances. Associating nodes with the Chef ensures the chef server installs the chef-client software on the nodes. 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).
Note: The minimum supported version of chef-client on nodes associated with OpsWorks for ChefAutomate Server is 12.16.42. We recommend running chef-client 13.6.4.
Chef – Node Bootstrapping
Using a knife to add or bootstrap an instance (See https://docs.chef.io/platforms.html for supported operating systems)
Example 1: Bootstrapping an instance using knife commands.
knife bootstrap windows winrm EnterNodeIPAddress --winrm-user Administrator --winrm-password 'enterserverpasswordhere' --node-name EnterNodeNamehere --run-list 'recipe[chef-client]'
Note: You can attach any cookbooks in place of the chef-client run-list or have a role uploaded to the chef server, which in turn has many run-lists attached to the role, and update the node run-list to use the newly created role. This topic will be discussed in a later stage(Chef – Node Bootstrapping).
Also see if you wish to add nodes automatically https://docs.aws.amazon.com/opsworks/latest/userguide/opscm-unattend-assoc.html
