Chef Server acts as the hub for configuration data.
It stores cookbooks, policies (applied to nodes), and metadata (describing every registered node managed by the chef-client).
To ask Chef Server for recipes, templates, file distributions and other configuration details, the chef-client is used by nodes.
Configuration work on the nodes is done by chef-client and not by the Chef Server. This type of approach is scalable, making the configuration effort distributed all throughout the organization.
July 15, 2015: Today we launched Chef Server 11 (HVM) version 11.1.7 at AWS Marketplace.
OS: Amazon Linux 2015.03 officially provided by AWS.
Chef Client Version: Chef-DK latest version (version 0.6.2-1) is installed, which includes chef-client 11.x at the beginning and registered as a Node of Chef-Server.
|EC2 instance type||Purpose||Compute Units (ECU)||Memory||Cores||*Price/hour|
|t2.large||development environment, db apps, web servers, for occasional burst*||2 units (burstable)||8 GB||2 cores||$0.15|
|c4.large||provides enhanced networking for higher packet per second (PPS) performance, lower network jitter, lower network latency||8 units||3.75 GB||2 cores||$0.13|
|m4.large||balance of compute, memory, network resources||6.5 units||8 GB||2 cores||$0.17|
*Price varies per region
*Burstable instances provides baseline CPU performance level and the ability to burst over the baseline. These instances are T2 family, M3, C3 and R3, which are all available in Chef Server 11 HVM. Launch them in any 9 global regions per hour.