AWS lexv2 documentation change
Summary
Fixed grammatical error ('a Amazon Lex' to 'an Amazon Lex') in example use case description
Security assessment
The change is a minor grammatical correction with no security implications. The content about selective logging for compliance remains unchanged.
Diff
diff --git a/lexv2/latest/dg/example-selective-logging.md b/lexv2/latest/dg/example-selective-logging.md index 34733ed28..7d69de8b2 100644 --- a//lexv2/latest/dg/example-selective-logging.md +++ b//lexv2/latest/dg/example-selective-logging.md @@ -11 +11 @@ Here is an example of a business use case for selective conversation log capture -A fintech company utilizes a Amazon Lex V2 bot to support their IVR system, which allows users to make bill payments. In order to meet compliance and auditing requirements, they must retain audio recordings of user-provided authorization consent. However, enabling general audio logs is not feasible as it would make them non-compliant, because it is not possible to obfuscate sensitive slots like CardNumber, CVV, and other information in the audio logs. Instead, they can enable selective conversation log capture for audio logs and set session attribute to only produce audio logs for utterance that has authorization consent. +A fintech company utilizes an Amazon Lex V2 bot to support their IVR system, which allows users to make bill payments. In order to meet compliance and auditing requirements, they must retain audio recordings of user-provided authorization consent. However, enabling general audio logs is not feasible as it would make them non-compliant, because it is not possible to obfuscate sensitive slots like CardNumber, CVV, and other information in the audio logs. Instead, they can enable selective conversation log capture for audio logs and set session attribute to only produce audio logs for utterance that has authorization consent.