- Newest
- Most votes
- Most comments
Based on your description, you're experiencing an issue where your SageMaker notebook instance appears to be running (as indicated by ongoing consumption), but you can't access it through the browser interface.
Here are some troubleshooting steps you can try:
-
Browser-related fixes: While you've already tried changing browsers and clearing cache, ensure you've completely cleared all cookies related to AWS services as well.
-
Check instance status: Verify in the AWS console that your notebook instance is actually in the 'InService' state. Sometimes instances can appear to be running but may have underlying issues.
-
Stop and restart the instance: This is often the most effective solution. Stop your notebook instance and then start it again without changing any configurations.
-
Check for old sessions: If you have any other browser tabs or CLI connections to the old SageMaker session still open, close them completely. Sometimes an old session can prevent a new one from properly establishing.
-
Network configuration: Check if there are any firewalls or network configurations that might be blocking traffic to your notebook instance.
-
Remove lifecycle configurations: If your notebook has custom lifecycle configurations, these might be causing issues. Consider updating your notebook instance to remove these customizations temporarily.
If none of these solutions work, you might need to contact AWS Support with specific details about your notebook instance, including the ARN, Jupyter and Python versions, and any relevant error messages from CloudWatch logs.
Sources
Sagemaker notebook instances inaccesible | AWS re:Post
Resolve missing output from cells in SageMaker AI notebook | AWS re:Post
Well, I stopped and started the instance and now is back, however I lost my current job.
answered a year ago
Relevant content
asked 5 years ago
