AWS sagemaker documentation change
Summary
Added troubleshooting section for cluster deletion failures related to permissions and policies
Security assessment
Documents required IAM permissions (sagemaker:ListComputeQuotas, sagemaker:DeleteComputeQuota, etc.) to resolve cluster deletion issues. While not fixing a disclosed vulnerability, it adds security-relevant documentation about proper permission configuration to prevent operational failures.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-governance-troubleshoot.md b/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-governance-troubleshoot.md index 3b4c66d69..ad8166b22 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-governance-troubleshoot.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-governance-troubleshoot.md @@ -5 +5 @@ -Dashboard tabTasks tabPolicies +Dashboard tabTasks tabPoliciesDeleting clusters @@ -18,0 +19,2 @@ The following page contains known solutions for troubleshooting your HyperPod EK + * Deleting clusters + @@ -65,0 +68,19 @@ To see more details into the failure, use the describe API. +## Deleting clusters + +The following lists known solutions to errors relating to deleting clusters. + + * When cluster deletion fails due to attached SageMaker HyperPod task governance policies, you will need to [Delete policies](./sagemaker-hyperpod-eks-operate-console-ui-governance-policies-delete.html). + + * When cluster deletion fails due to the missing the following permissions, you will need to update your cluster administrator minimum set of permissions. See the **Amazon EKS** tab in the [IAM users for cluster admin](./sagemaker-hyperpod-prerequisites-iam.html#sagemaker-hyperpod-prerequisites-iam-cluster-admin) section. + + * `sagemaker:ListComputeQuotas` + + * `sagemaker:ListClusterSchedulerConfig` + + * `sagemaker:DeleteComputeQuota` + + * `sagemaker:DeleteClusterSchedulerConfig` + + + +