How do I troubleshoot errors that occur when I migrate from SageMaker Studio Classic to SageMaker Studio?

Resolution

First, confirm that you met all the prerequisites to migrate the Studio experience.

If you met all the prerequisites, then troubleshoot your issue based on the error that you receive.

Parameter validation error

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. 

If you're using AWS CLI version 1, then you might receive the following error message:

"Parameter validation failed:
Unknown parameter in DefaultUserSettings: "StudioWebPortal", must be one of: ExecutionRole, SecurityGroups, SharingSettings, JupyterServerAppSettings, KernelGatewayAppSettings, TensorBoardAppSettings, RStudioServerProAppSettings, RSessionAppSettings
Unknown parameter in DefaultUserSettings: "DefaultLandingUri", must be one of: ExecutionRole, SecurityGroups, SharingSettings, JupyterServerAppSettings, KernelGatewayAppSettings, TensorBoardAppSettings, RStudioServerProAppSettings, RSessionAppSettings"

To resolve the preceding error, complete the following steps:

1. Install or update the AWS CLI to the latest version.

2. Run the following command to confirm the installation:

   aws --version

3. Retry your migration from SageMaker Classic Studio to SageMaker Studio.

Access denied exception error

If the AWS Identity and Access Management (IAM) role that's associated with your domain has trust relationships with multiple services, then you might receive the following error message:

"AccessDeniedException: Role XXXXXXXXXXXXXXXXX trusts too many services, expected only 1"

To resolve the preceding error, complete the following steps:

1. Open the IAM console.

2. Identify the IAM role that has trust relationships with multiple services.

3. Edit the trust relationships policy to include only sagemaker.amazonaws.com:

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Principal": {
           "Service": "sagemaker.amazonaws.com"
         },
         "Action": "sts:AssumeRole"
       }
     ]
   }

4. Save your changes. Then, retry the migration from SageMaker Classic Studio to SageMaker Studio.

If you encounter other access denied errors during migration, then review your IAM roles and policies. Use AWS CloudTrail to identify specific permission issues. To filter your CloudTrail log, use the event source lookup attribute with the sagemaker.amazonaws.com value.