AWS prescriptive-guidance documentation change
Summary
Updated image path and removed detailed application flow steps (Lambda authorizer interaction with DynamoDB and Verified Permissions)
Security assessment
The modifications involve documentation structure and image references rather than security content. No security vulnerabilities, mitigations, or policy changes are addressed in the removed flow details.
Diff
diff --git a/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/external-data-avp.md b/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/external-data-avp.md index 3021b1f3c..7d1aa512a 100644 --- a//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/external-data-avp.md +++ b//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/external-data-avp.md @@ -13,14 +13 @@ The following diagram shows an example of how additional data can be retrieved a - - -**Application flow:** - - 1. The application receives an API call to Amazon API Gateway and forwards the call to the AWS Lambda authorizer. - - 2. The Lambda authorizer calls Amazon DynamoDB to retrieve additional data about the principal that made the request. - - 3. The Lambda authorizer incorporates the additional data into the authorization request that was made to Verified Permissions. - - 4. The Lambda authorizer makes an authorization request to Verified Permissions and receives an authorization decision. - - - +