2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
This is a bug that we also discovered early this morning. A fix has been submitted and is currently rolling out to all regions.
To access Graph Explorer, for now, go to the SageMaker console and open the Notebook instance as if you're opening it to use Jupyter. After Jupyter is open, change the URL to:
https://<your_notebook_endpoint>/proxy/9250/explorer/
That should open Graph Explorer.
répondu il y a 5 mois
0
I tried this, and it does boot into Graph Explorer, but I'm now stuck in a loop where its asking me to synchronize my database, then fails everytime.
répondu il y a 5 mois
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a 9 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 4 ans
Looks like the original issue should be fixed now. If you pull up developer tools in your browser, which request do you see failing and what is the error response that you're seeing? Are you seeing any issues when using the Jupyter magics from the same instance (able to validate connectivity)?