AWS vpc-lattice: Fix broken link to confused deputy documentation
Summary
Corrected URL formatting for confused deputy documentation link.
Security assessment
Change fixes a broken hyperlink but doesn't alter security content; confused deputy risk was already documented.
Evidence
+To use other AWS services that VPC Lattice is integrated with and the entire suite of VPC Lattice features, you must have specific additional permissions. These permissions are not included in the `VPCLatticeFullAccess` managed policy because of the [confused deputy](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) privilege escalation risk.
Diff
diff --git a/vpc-lattice/latest/ug/security_iam_id-based-policies.md b/vpc-lattice/latest/ug/security_iam_id-based-policies.md index bd320f27d..244f3463f 100644 --- a//vpc-lattice/latest/ug/security_iam_id-based-policies.md +++ b//vpc-lattice/latest/ug/security_iam_id-based-policies.md @@ -49 +49 @@ For more information about best practices in IAM, see [Security best practices i -To use other AWS services that VPC Lattice is integrated with and the entire suite of VPC Lattice features, you must have specific additional permissions. These permissions are not included in the `VPCLatticeFullAccess` managed policy because of the [confused deputy](https://docs.aws.amazon.com//IAM/latest/UserGuide/confused-deputy.html) privilege escalation risk. +To use other AWS services that VPC Lattice is integrated with and the entire suite of VPC Lattice features, you must have specific additional permissions. These permissions are not included in the `VPCLatticeFullAccess` managed policy because of the [confused deputy](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) privilege escalation risk.