AWS sagemaker documentation change

Service: sagemaker · 2025-10-22 · Documentation low

File: sagemaker/latest/dg/infrastructure-security.md

Summary

Removed a sentence explaining that requests must be signed using IAM access keys or temporary credentials from AWS STS

Security assessment

The removed content described standard security practices for API authentication but did not address a specific vulnerability or incident. This appears to be a documentation simplification rather than a security fix.

Diff

diff --git a/sagemaker/latest/dg/infrastructure-security.md b/sagemaker/latest/dg/infrastructure-security.md
index 29682a15f..6ca8d614e 100644
--- a//sagemaker/latest/dg/infrastructure-security.md
+++ b//sagemaker/latest/dg/infrastructure-security.md
@@ -20,2 +19,0 @@ You use AWS published API calls to access Amazon SageMaker AI through the networ
-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.
-