AWS emr high security documentation change
Summary
Removed a sentence explaining that requests must be signed with IAM access keys/secret keys or AWS STS temporary credentials.
Security assessment
The removed content specifically described fundamental security controls (authentication via access keys or temporary credentials). Removing this documentation could lead to misunderstandings about authentication requirements, potentially weakening security practices. This directly impacts security guidance for API access to EMR.
Diff
diff --git a/emr/latest/ManagementGuide/infrastructure-security.md b/emr/latest/ManagementGuide/infrastructure-security.md index 722f9a52f..907cbbda9 100644 --- a//emr/latest/ManagementGuide/infrastructure-security.md +++ b//emr/latest/ManagementGuide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Amazon EMR through the network. Client -Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html) (AWS STS) to generate temporary security credentials to sign requests. -