https://github.com/aws/aws-emr-containers-best-practices

Best practices and recommendations for getting started with Amazon EMR on EKS.
https://github.com/aws/aws-emr-containers-best-practices

Last synced: about 1 month ago
JSON representation

Best practices and recommendations for getting started with Amazon EMR on EKS.

• Host: GitHub
• URL: https://github.com/aws/aws-emr-containers-best-practices
• Owner: aws
• License: other
• Created: 2020-12-23T19:57:27.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2024-08-26T22:38:19.000Z (3 months ago)
• Last Synced: 2024-10-04T21:06:27.495Z (about 1 month ago)
• Language: Python
• Homepage: https://aws.github.io/aws-emr-containers-best-practices
• Size: 24.7 MB
• Stars: 59
• Watchers: 11
• Forks: 27
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
## Amazon EMR on Amazon EKS 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](https://aws.github.io/aws-emr-containers-best-practices/).

## 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](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository)

2. Make your change and double-check the [mkdocs.yml](./mkdocs.yml) is updated accordingly.

3. Install the MkDocs command tool and material theme if needed:

```bash

pip install mkdocs

pip install mkdocs-material # material theme

```

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:

```bash

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:

```bash

mkdocs build

```

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

```bash

ls site

```

9. Commit change to github and send us a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork).

10. With a repo admin permission, we can merge the pull request into the main branch.

11. Most importantly, as a repo admin, we must run the deploy command to copy the './site' content to 'gh-pages' branch and pushing to GitHub. Without this step, the website content won't be refreshed.

```bash

mkdocs gh-deploy

```