AWS Route53 documentation change
Summary
Removed a paragraph explaining that API requests must be signed with IAM credentials or temporary STS credentials
Security assessment
The removed content described standard AWS authentication mechanisms but did not address a specific vulnerability. While authentication is security-related, the removal appears to be a documentation simplification rather than a response to a security incident.
Diff
diff --git a/Route53/latest/DeveloperGuide/infrastructure-security.md b/Route53/latest/DeveloperGuide/infrastructure-security.md index a632b3e14..e4cf5f166 100644 --- a//Route53/latest/DeveloperGuide/infrastructure-security.md +++ b//Route53/latest/DeveloperGuide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Route 53 through the network. Clients -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. -