AWS prescriptive-guidance documentation change
Summary
Restructured content sections and changed 'Using Amazon Verified Permissions' to 'Design models for Amazon Verified Permissions'
Security assessment
Content reorganization and heading updates. No security-related modifications or vulnerability fixes.
Diff
diff --git a/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/design-models.md b/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/design-models.md index 0b68231d7..d0d214156 100644 --- a//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/design-models.md +++ b//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/design-models.md @@ -11,9 +10,0 @@ There are many ways to implement API access control and authorization. This guid -###### Design models: - - * [Design models for Amazon Verified Permissions](./using-avp.html) - - * [Design models for OPA](./using-opa.html) - - - - @@ -28 +19 @@ Implementing a PEP -Using Amazon Verified Permissions +Design models for Amazon Verified Permissions