AWS vpc-lattice documentation change
Summary
Removed a sentence about requiring signed requests using access keys or STS temporary credentials
Security assessment
The removed content described standard AWS security practices but didn't address a specific vulnerability. This appears to be a documentation simplification rather than a security fix.
Diff
diff --git a/vpc-lattice/latest/ug/infrastructure-security.md b/vpc-lattice/latest/ug/infrastructure-security.md index 892924591..0b9c0b852 100644 --- a//vpc-lattice/latest/ug/infrastructure-security.md +++ b//vpc-lattice/latest/ug/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access VPC Lattice through the network. Clien -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. -