AWS IAM: Fixed broken URLs in troubleshooting documentation
Summary
Corrected two malformed hyperlinks: VPC endpoint policy and toolkit documentation URLs.
Security assessment
The change fixes broken URLs but doesn't alter security guidance or address vulnerabilities.
Evidence
- * If you're using an [Amazon VPC endpoint policy](https://docs.aws.amazon.com//vpc/latest/privatelink/vpc-endpoints-access.html) and you get an access denied error that is not logged in AWS CloudTrail, it might be because the VPC endpoint owner account is different from the calling account or target role account.
Diff
diff --git a/IAM/latest/UserGuide/troubleshoot_access-denied.md b/IAM/latest/UserGuide/troubleshoot_access-denied.md index 836866e5b..967dd3c0b 100644 --- a//IAM/latest/UserGuide/troubleshoot_access-denied.md +++ b//IAM/latest/UserGuide/troubleshoot_access-denied.md @@ -55 +55 @@ In this case, Mateo must ask his administrator to update his policies to allow a - * If you're using an [Amazon VPC endpoint policy](https://docs.aws.amazon.com//vpc/latest/privatelink/vpc-endpoints-access.html) and you get an access denied error that is not logged in AWS CloudTrail, it might be because the VPC endpoint owner account is different from the calling account or target role account. + * If you're using an [Amazon VPC endpoint policy](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html) and you get an access denied error that is not logged in AWS CloudTrail, it might be because the VPC endpoint owner account is different from the calling account or target role account. @@ -66 +66 @@ In this case, Mateo must ask his administrator to update his policies to allow a - * Verify that your requests are being signed correctly and that the request is well-formed. For details, see your [toolkit](https://docs.aws.amazon.com/http://aws.amazon.com/developer/tools/) documentation or [Use temporary credentials with AWS resources](./id_credentials_temp_use-resources.html). + * Verify that your requests are being signed correctly and that the request is well-formed. For details, see your [toolkit](http://aws.amazon.com/developer/tools/) documentation or [Use temporary credentials with AWS resources](./id_credentials_temp_use-resources.html).