2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 5 mesi fa
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.
con risposta 5 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 anni fa
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)?