AWS emr documentation change
Summary
Updated documentation about IAM policy formatting requirements and character limits
Security assessment
The changes clarify existing policy requirements but do not introduce new security controls or address vulnerabilities. The character limit clarification relates to policy syntax constraints rather than security posture improvements.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-cli-execution.md b/emr/latest/EMR-Serverless-UserGuide/jobs-cli-execution.md index b2bdbd93b..a12f38fa9 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-cli-execution.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-cli-execution.md @@ -98 +98 @@ It's possible to specify both an inline IAM policy and managed policy ARNs in th - * The inline IAM policy string specified in the `execution-iam-policy`'s `policy` field has to conform to the json string standard, with no newlines and quotes escaped as in the example above. + * The inline IAM policy string specified in the `execution-iam-policy`'s `policy` field has to conform to the json string standard, with no newlines and quotes escaped as in the preceding example. @@ -104 +104 @@ It's possible to specify both an inline IAM policy and managed policy ARNs in th - * When both inline IAM policy and managed policies are used, the plaintext that you use for both the inline and managed policies combined can't exceed 2,048 characters. + * When both inline IAM policy and managed policies are used, the plaintext that you use for the inline and managed policies combined can't exceed 2,048 characters.