AWS transcribe documentation change
Summary
Simplified explanation of default IAM permissions by removing explicit mention of AWS Management Console, CLI, and API access restrictions
Security assessment
The change removes specific references to access methods (Console/CLI/API) but does not alter the security posture or address any vulnerability. It maintains the core security principle of least privilege by default.
Diff
diff --git a/transcribe/latest/dg/security_iam_id-based-policy-examples.md b/transcribe/latest/dg/security_iam_id-based-policy-examples.md index c41ca39ea..7fc7a30a1 100644 --- a//transcribe/latest/dg/security_iam_id-based-policy-examples.md +++ b//transcribe/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the AWS Management ConsolePermissions required for IA -By default, users and roles don't have permission to create or modify Amazon Transcribe 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 Transcribe resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.