elasticsearch-opsworks Cookbook

This cookbook installs and configures Elasticsearch, on AWS OpsWorks.

Requirements

• Java is required by ES; This cookbook will install OpenJDK 7.
• Instances must belong to a single OpsWorks layer in order for configuration to work correctly.

Attributes

elasticsearch-opsworks::default

Key	Type	Description	Default	Required?
['elasticsearch']['version']	string	The version of Elasticsearch to install	1.3.4	No
['elasticsearch']['auth']['username']	string	Username for Nginx HTTP Basic Authorization	elasticsearch_user	No, but recommended
['elasticsearch']['auth']['password']	string	Password for Nginx HTTP Basic Authorization. (Use the plain text password)	elasticsearch_password	No, but recommended
['elasticsearch']['ssl']['cert']	string	The contents of Nginx's ssl_certificate file	nil	No, but recommended
['elasticsearch']['ssl']['key']	string	The The contents of Nginx's ssl_certificate_key file	nil	No, but recommended
['elasticsearch']['path']['logs']	string	The file path to store the logs	/var/log/elasticsearch	No, but recommended
['elasticsearch']['path']['data']	string	Where ES stores its data (hint: you'll likely want this on an EBS)	/var/data/elasticsearch	No

Usage

elasticsearch-opsworks::default

TODO: Write usage instructions for each cookbook.

e.g. Just include elasticsearch-opsworks in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[elasticsearch-opsworks]"
  ]
}

Contributing

TODO: (optional) If this is a public cookbook, detail the process for contributing. If this is a private cookbook, remove this section.

e.g.

1. Fork the repository on Github
2. Create a named feature branch (like add_component_x)
3. Write your change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

License and Authors

Authors: TODO: List authors