AWS amazonq documentation change
Summary
Updated URL formatting for confused deputy problem documentation link
Security assessment
Identical to the previous entry - URL correction without substantive security content changes. The existing security recommendations about access control remain unchanged.
Diff
diff --git a/amazonq/latest/qbusiness-ug/cde-lambda-operations.md b/amazonq/latest/qbusiness-ug/cde-lambda-operations.md index 7c96e0226..0e6a96148 100644 --- a//amazonq/latest/qbusiness-ug/cde-lambda-operations.md +++ b//amazonq/latest/qbusiness-ug/cde-lambda-operations.md @@ -387 +387 @@ JSON -We recommend that you include `aws:sourceAccount` and `aws:sourceArn` in the trust policy. Their inclusion limits permissions and securely checks if `aws:sourceAccount` and `aws:sourceArn` are the same values as provided in the IAM role policy for the `sts:AssumeRole` action. This approach prevents unauthorized entities from accessing your IAM roles and their permissions. For more information, see [confused deputy problem](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) in the _IAM User Guide_. +We recommend that you include `aws:sourceAccount` and `aws:sourceArn` in the trust policy. Their inclusion limits permissions and securely checks if `aws:sourceAccount` and `aws:sourceArn` are the same values as provided in the IAM role policy for the `sts:AssumeRole` action. This approach prevents unauthorized entities from accessing your IAM roles and their permissions. For more information, see [confused deputy problem](https://docs.aws.amazon.com//IAM/latest/UserGuide/confused-deputy.html) in the _IAM User Guide_.