rajender16kumar / aws-emr-best-practices

A best practices guide for using AWS EMR. The guide will cover best practices on the topics of cost, performance, security, operational excellence, reliability and application specific best practices across Spark, Hive, Hudi, Hbase and more.

Amazon EMR on Amazon Best Practices

A best practices guide for submitting spark applications, integration with hive metastore, security, storage options, debugging options and performance considerations.

Return to Live Docs.

License Summary

The documentation is made available under the Creative Commons Attribution-ShareAlike 4.0 International License. See the LICENSE file.

The sample code within this documentation is made available under the MIT-0 license. See the LICENSE-SAMPLECODE file.

How to make a change

1. Fork the repository
2. Make your change and double check the mkdocs.yml is updated accordingly.
3. Install the MkDocs command tool if needed:

pip install mkdocs
pip install mkdocs-material

4. MkDocs comes with a built-in dev-server that lets you preview your documentation as you work on it. Make sure you're in the same directory as the mkdocs.yml configuration file, then run the command:

mkdocs serve

5. Open up http://127.0.0.1:8000/ in your browser, and you'll see the best practice website being displayed locally.
6. Adjust your document changes in real time.
7. When everything looks good and you're ready to deploy the change, run the command to build/compile the website content:

mkdocs build

8. This will refresh the directory site. Take a look inside the directory and make sure your changes are included.

ls site

9. Commit change to github and send us a pull request.