AWS lambda documentation change
Summary
Removed a sentence explaining that requests must be signed with access keys or temporary credentials from AWS STS
Security assessment
The removed content was general security best practice documentation rather than addressing a specific vulnerability. While it relates to authentication mechanisms, there is no evidence this change fixes a security issue or introduces new security features.
Diff
diff --git a/lambda/latest/dg/security-infrastructure.md b/lambda/latest/dg/security-infrastructure.md index 739392e00..5529ae33e 100644 --- a//lambda/latest/dg/security-infrastructure.md +++ b//lambda/latest/dg/security-infrastructure.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Lambda through the network. Clients mu -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. -