- Newest
- Most votes
- Most comments
If the notebook is attached to cluster and if you are still encountering this error, it probably means notebook is unable to communicate to EMR Cluster's JupyterEnterpriseGateway(JEG) endpoint. Please make sure your EMR cluster / notebook security groups are not restrictive. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-notebooks-security-groups.html
you may check logs on your EMR cluster on /var/log/applications/Jupyter*
Unfortunately, you will not able to see logs on EMR notebooks as its managed by EMR service.
if this is working differently between versions, Please make sure you review these
EMR Studio Considerations : https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-studio-considerations.html
EMR Notebook Considerations : https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-notebooks-considerations.html
Relevant content
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago