AWS sagemaker-unified-studio documentation change
Summary
Removed mention of specific interfaces (console/CLI/API) from default permissions statement. Simplified explanation of default permissions for SageMaker Unified Studio resources.
Security assessment
The change removes redundant information about access methods but doesn't alter security recommendations or address vulnerabilities. It maintains the core security principle of least privilege by emphasizing default deny state for resource modifications.
Diff
diff --git a/sagemaker-unified-studio/latest/adminguide/security_iam_id-based-policy-examples.md b/sagemaker-unified-studio/latest/adminguide/security_iam_id-based-policy-examples.md index 49f425c44..5290bb5b8 100644 --- a//sagemaker-unified-studio/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//sagemaker-unified-studio/latest/adminguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Amazon SageMaker Unified Studio resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Amazon SageMaker Unified Studio resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.