AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-07-10 · Documentation low

File: prescriptive-guidance/latest/saas-multitenant-api-access-authorization/custom-policy-engine.md

Summary

Added italic formatting to 'policy decoupling'

Security assessment

Formatting change only. No security implications or documentation additions.

Diff

diff --git a/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/custom-policy-engine.md b/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/custom-policy-engine.md
index 20a423246..8b00ce786 100644
--- a//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/custom-policy-engine.md
+++ b//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/custom-policy-engine.md
@@ -9 +9 @@
-An alternative method for implementing a PDP is to create a custom policy engine. The goal of this policy engine is to decouple authorization logic from an application. The custom policy engine is responsible for making authorization decisions, similar to Verified Permissions or OPA, to achieve policy decoupling. The primary difference between this solution and using Verified Permissions or OPA is that the logic for writing and evaluating policies is custom-built for a custom policy engine. Any interactions with the engine must be exposed through an API or some other method to enable authorization decisions to reach an application. You can write a custom policy engine in any programming language or use other mechanisms for policy evaluation, such as the [Common Expression Language (CEL)](https://opensource.google/projects/cel).
+An alternative method for implementing a PDP is to create a custom policy engine. The goal of this policy engine is to decouple authorization logic from an application. The custom policy engine is responsible for making authorization decisions, similar to Verified Permissions or OPA, to achieve _policy decoupling_. The primary difference between this solution and using Verified Permissions or OPA is that the logic for writing and evaluating policies is custom-built for a custom policy engine. Any interactions with the engine must be exposed through an API or some other method to enable authorization decisions to reach an application. You can write a custom policy engine in any programming language or use other mechanisms for policy evaluation, such as the [Common Expression Language (CEL)](https://opensource.google/projects/cel).