search

aws-samples / sagemaker-studio-apps-lifecycle-config-examples

MIT No Attribution
23 stars 8 forks source link

Studio Misconfigured After trying the LCC #3

Closed ArtemioPadilla closed 7 months ago

ArtemioPadilla commented 7 months ago

Hello,

After I tried this LCC my studio began bugging. I cannot tell for certain if this is an issue with the LCC or is another issue with the new Studio experience.

After I tryed to apply the LCC I cannot longer see the instance types or images in the new studio Spaces.

image

I see in CloudTrail an error that says:

ValidationException - "1 validation error detected: Value null at 'spaceSettings.codeEditorAppSettings.defaultResourceSpec.ec2InstanceType' failed to satisfy constraint: Member must not be null"

If I describe the space I can see these settings which do not contain the ec2InstanceType param

"SpaceSettings": { "CodeEditorAppSettings": { "DefaultResourceSpec": { "SageMakerImageArn": "arn:aws:sagemaker:us-east-1:885854791233:image/sagemaker-distribution-cpu", "SageMakerImageVersionAlias": "1.3.0", "InstanceType": "ml.t3.medium" } }

Any ideas on how to fix this problem without deleting the domain?

This issue is also posted in this AWS forum

ArtemioPadilla commented 7 months ago

After further debugging, I believe the problem originated from a lack of permissions on ECR. The events on CloudTrail do not show these errors, but my problem was resolved by granting privileges on ECR.