1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hello,
Thank you for using Amazon SageMaker Studio.
Usually this kind of error is occurred due to internal issues when trying to launch the Studio where the Sagemaker Service is trying to create default JupyterServer App on your behalf. To identify the root cause of this issue, we will need to get the details about the SageMaker Studio domain id or arn along with the user profile name on which the error was encountered. For further investigation on this issue, I'd recommend you to open a case with SageMaker Premium Support team so that you can share above mentioned details securely.
Open a support case with AWS using the link:
関連するコンテンツ
AWS公式更新しました 1年前- AWS公式更新しました 6ヶ月前
If you have sufficient permissions, you can also look at Cloudwatch logs to identify the error. You can look for /aws/sagemaker/studio log group and filter by your user profile name and the default app log stream.