aws / aws/amazon-sagemaker-examples
04_Ingest_data_with_EMR.ipynb[Content Improvement]
- Dominant language
- Jupyter Notebook
- Stars
- 11k
- Forks
- 7k
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 8
Description
**Link to the notebook**
https://github.com/aws/amazon-sagemaker-examples/blob/master/ingest_data/04_Ingest_data_with_EMR.ipynb
**What aspects of the notebook can be improved?**
For connecting Sagemaker to EMR there are two methods suggested - "documentation and procedure".
I tested both and both work but you only need one.
It seems to reader that they have to follow and setup both.
Also first method from AWS blog is rather complicated (creating new VPC, etc.).
It may have few advantages but is not user friendly.
**What are your suggestions?**
Recommend using second method from
https://docs.aws.amazon.com/sagemaker/latest/dg/nbi-lifecycle-config-emr.html
Contributor guide
Research direction
Open ingest_data/04_Ingest_data_with_EMR.ipynb and review the two described methods for connecting SageMaker to EMR, including the linked AWS documentation. Clarify that readers should use one method, recommend the lifecycle-configuration approach, and ensure the notebook no longer suggests that both procedures are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter-notebook
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100