2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Amazon Lex provides Slot Obfuscation where Amazon Lex enables you to obfuscate, or hide, the contents of slots so that the content is not visible. To protect sensitive data captured as slot values, you can enable slot obfuscation to mask those values in conversation logs. See Slot Obfuscation.
Also, for encryption, Lex encrypts the data at rest as well as in transit.
con risposta 2 anni fa
0
Hi , Thanks for your answer, I tried it with Slot Obfuscation approach , it was working with sensitive data from slot values as masked in conversional logs, Is there any way to mask the cloudwatch logs same like conversation logs when lambda is invoked from same Intent (bot).
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
The feature to redact sensitive information from CloudWatch logs does not exist today. There is a feature request internally within AWS for the same. You can write the same logs with redacted information to another log stream or log group and delete the original one. However, that can cost for CW logs collect, data transfer, and data store (and lambda or other services used to run the code if that's one of the aws services) Amazon CloudWatch pricing. This is a third-party article but I see a sample solution from here https://medium.com/@likhita507/editing-cloud-watch-logs-without-using-log-streams-bdbe95662967. Please use it at your discretion.