Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


chef-server-rds (2) Versions 1.0.1

Installs and configures Chef Server backed by Amazon RDS Postgresql

cookbook 'chef-server-rds', '~> 1.0.1', :supermarket
cookbook 'chef-server-rds', '~> 1.0.1'
knife supermarket install chef-server-rds
knife supermarket download chef-server-rds
Quality 71%

Chef Server backed by AWS RDS

This cookbook configures a system to be a Chef Server using Amazons RDS for the postgresql database.

Given an iam key and secret, it will provision the rds instance if it doesn't exist in the account, initialize the chef server schema, and install the appropriate platform-specific chef-server Omnibus package and perform the initial configuration of Chef Server on an AWS elastic compute ubuntu instance.

Using postgres on Amazon RDS offloads DB resource use away from the chef-server host. It also enables various DB functions like scaling, backup, and restore to be done independently of the chef-server installations. Similar configurations can be written for other db service providers.


The cookbook has been tested on the following OS
* Ubuntu 12.04, 12.10 64-bit

The role below depends on the following cookbooks
* aws_rds

* postgresql
* build-essential

Here's a sample chef role that uses the cookbook

name "chef-server-rds"
description "chef-server-rds"
  "build_essential" => {
    "compiletime" => true
  "chef-server" => {
    "configuration" => {
     "notification_email" => "",
       "postgresql" => {
          "enable" => false
    "nginx" => {
       "enable_non_ssl" => true,
    "postgresql" => {
      "enable" => false,
  "rds" => {
    "id" => 'opscodechef',
    "dbname" => 'opscode_chef',
    "username" => 'test_user',
    "password" => 'test_password',
    "key" => 'iam_key',
    "secret" => 'iam_secret'

The role can then simply be run to configure both the RDS instance and the chef-server that uses it

knife ec2 server create -r "role[chef-server-rds]" -I ami-b66ca0de -G xyzGroup -S xyzKey -x ubuntu -f m3.medium -N chef_server_name

Dependent cookbooks

aws_rds >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

chef-server-rds cookbook README


  • Cleanup changelog and release versions


  • Initial release

Collaborator Number Metric

1.0.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

1.0.1 passed this metric

Foodcritic Metric

1.0.1 failed this metric

FC007: Ensure recipe dependencies are reflected in cookbook metadata: chef-server-rds/recipes/dev.rb:16
FC009: Resource attribute not recognised: chef-server-rds/recipes/default.rb:95
FC064: Ensure issues_url is set in metadata: chef-server-rds/metadata.rb:1
FC065: Ensure source_url is set in metadata: chef-server-rds/metadata.rb:1
FC066: Ensure chef_version is set in metadata: chef-server-rds/metadata.rb:1
FC069: Ensure standardized license defined in metadata: chef-server-rds/metadata.rb:1
FC109: Use platform-specific package resources instead of provider property: chef-server-rds/recipes/default.rb:95
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

1.0.1 passed this metric

Supported Platforms Metric

1.0.1 passed this metric

Testing File Metric

1.0.1 passed this metric

Version Tag Metric

1.0.1 passed this metric