- Newest
- Most votes
- Most comments
Hi , Can you run DescribeProject action [1] against the project and confirm what is the ProjectStatus. From CLI you can run: aws sagemaker describe-project --project-name <value> . The response from the above command will include a "ProvisionedProductStatusMessage" which will explain why the deletion failed. The issue might be related to missing IAM permissions. Your sagemaker execution role needs to have the following policy statement in the AmazonSageMakerFullAccess policy [2]:
{ "Effect": "Allow", "Action": [ "servicecatalog:TerminateProvisionedProduct", "servicecatalog:UpdateProvisionedProduct" ], "Resource": "*", },
Another potential factor could be that, during the deletion of the project, Service Catalog attempted to assume a role which was attached the service catalogue product but encountered a failure in assuming the role. To troubleshoot this issue, please verify the existence of the roles. If the roles are not found, consider re-creating them in your account. Ensure that the newly created roles have identical names and permissions as the roles that were deleted.
After that try deleting the projects again using: aws sagemaker delete-project --project-name <value>
Reference [1] https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/describe-project.html [2] https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsservicecatalog.html#awsservicecatalog-servicecatalog_userLevel [3] https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/delete-project.html
Relevant content
- asked 5 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago