AWS emr documentation change
Summary
Clarified example service (AWS KMS) in documentation about IAM role permissions for non-IAM Identity Center integrated services
Security assessment
The change provides additional clarity about AWS KMS in existing security context but does not introduce new security documentation or address a specific security issue. It's a minor editorial improvement to existing guidance.
Diff
diff --git a/emr/latest/ManagementGuide/emr-idc-start.md b/emr/latest/ManagementGuide/emr-idc-start.md index c468e9d0d..390a7e3ef 100644 --- a//emr/latest/ManagementGuide/emr-idc-start.md +++ b//emr/latest/ManagementGuide/emr-idc-start.md @@ -112 +112 @@ If the role doesn't have trusted credentials and accesses a Lake Formation-prote -AWS credentials that use Trusted Identity Propagation the IAM policies defined in the IAM role for any calls made to services not integrated with IAM Identity Center. This includes, for example, the AWS Key Management Service. Your role should also define any IAM permissions for any such services you would attempt to access. Currently supported IAM Identity Center integrated services include AWS Lake Formation and Amazon S3 Access Grants. +AWS credentials that use Trusted Identity Propagation the IAM policies defined in the IAM role for any calls made to services not integrated with IAM Identity Center. This includes, for example, the AWS Key Management Service. Your role should also define any IAM permissions for any such services you would attempt to access example AWS Key Management Service. Currently supported IAM Identity Center integrated services include AWS Lake Formation and Amazon S3 Access Grants.