awslabs / awslabs/amazon-emr-cli
Add the ability to start a local EMR dev environment
- Dominant language
- Python
- Stars
- 47
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Currently the `amazon-emr-vscode-toolkit` provide a way to write your code on an EMR environment on your local machine leveraging the EMR on EKS container image with devcontainer.
This is limited to IDEs that support devcontainer. It would be good to have a standalone implementation from within the EMR CLI to start a local dev environment a mount the project as a volume to the docker container of the EMR image.
This feature would be interesting for PyCharm that offer a way to connect to a remote [jupyter server](https://www.jetbrains.com/help/pycharm/configuring-jupyter-notebook.html?_gl=1*1e4wmkc*_ga*MTcwMjIwNTAzMC4xNjgxOTQyODYw*_ga_9J976DJZ68*MTY4MTk0Mjg1OS4xLjEuMTY4MTk0Mjg4Mi4wLjAuMA..&_ga=2.91528538.1974745293.1681942860-1702205030.1681942860#configure-server)
Contributor guide
Research direction
Start by reading the existing amazon-emr-vscode-toolkit devcontainer flow and the EMR CLI entry points. Define how the standalone CLI should start the local EMR image and mount the project as a volume. Done means the environment starts without devcontainer support and can be used with PyCharm through its remote Jupyter server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, jupyter-notebook, python
- Domain
- cli, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100