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

RSS

et_nat (12) Versions 3.1.0

Apache v2.0

Policyfile
Berkshelf
Knife
cookbook 'et_nat', '= 3.1.0', :supermarket
cookbook 'et_nat', '= 3.1.0'
knife supermarket install et_nat
knife supermarket download et_nat
README
Dependencies
Quality 0%

et_nat cookbook

Build Status
Cookbook Version

A cookbook to provide a NAT for an EC2 VPC (with HA if desired)

Requirements

  • An EC2 VPC
  • 1 VPC node for a simple NAT or 3 VPC nodes for HA

Usage

When creating instances using this cookbook, in order to assign a public IP address in your VPC, you’ll want to use a command like this:

knife ec2 server create \
    -E prod \
    -N prod-nat \
    -s subnet-xxxxxxxx \
    -f c3.large \
    -g sg-xxxxxxxx \
    -r "recipe[xyz]" \
    --iam-profile nat-ha \
    --associate-public-ip

The --associate-public-ip is especially crucial, as otherwise, the instance will be unable to connect out, nor will it function as a NAT.

Network Configuration

Attributes

  • ['nat']['yaml']['mocking']: Default value is true
  • ['nat']['yaml']['monitor_enabled']: Default value is false
  • ['nat']['search_string'] = Default value is 'run_list:recipe\[et_nat\]'

Recipes

default

  • Installs Fog for making AWS API calls
  • Uses the other two recipes in this cookbook to set up the NAT mechanisms

ha

  • Provides mechanisms for maintaining high availability of a cluster of NAT instances using Chef Search & a NAT monitor script
  • Can set up snitch-style monitoring using Cronitor
    • Specify monitor_token and monitor_opts in your YAML config to create a new Cronitor monitor
    • Specify monitor_code to use an existing Cronitor monitor
    • See the cronitor gem docs for details on what these fields expect

iptables

  • Does the bulk of the work to set up the NAT

Author

Author:: EverTrue (devops@evertrue.com)

Dependent cookbooks

et_fog ~> 1.2
magic ~> 1.1

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Foodcritic Metric
            

3.1.0 failed this metric

FC003: Check whether you are running with chef server before using server-specific features: /tmp/cook/ebc92f5ef61b9325dd739fe2/et_nat/recipes/ha.rb:1