AWS emr documentation change
Summary
Removed details about requiring signed API requests using access keys or AWS STS
Security assessment
The removed content described standard security practices for API requests but does not indicate a specific security vulnerability being addressed. This appears to be a documentation simplification rather than a security fix.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/infrastructure-security.md b/emr/latest/EMR-Serverless-UserGuide/infrastructure-security.md index a95f15fbc..440ecbc98 100644 --- a//emr/latest/EMR-Serverless-UserGuide/infrastructure-security.md +++ b//emr/latest/EMR-Serverless-UserGuide/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. -