AWS Security ChangesHomeSearch

AWS connect: Update Contact Lens conversational analytics error code descriptions

Service: connect · 2026-09-27 · Documentation low

File: connect/latest/adminguide/contact-lens-error-notifications.md

Summary

Revises RECORDING_FILE_CANNOT_BE_READ and RECORDING_FILE_TOO_SMALL descriptions (threshold changed to 500 ms), removes a duplicate RECORDING_FILE_CANNOT_BE_READ entry, and adds new error codes UNSUPPORTED_RECORDING_FORMAT, ANALYSIS_FILES_CANNOT_BE_WRITTEN, and MAX_PACKAGE_FEATURE_ONLY.

Security assessment

This is a documentation update to error-code reference tables for Contact Lens analytics, including a permissions-related error message. It mentions permissions only as a troubleshooting cause and does not document a security feature or address a specific vulnerability.

Evidence

ANALYSIS_FILES_CANNOT_BE_WRITTEN | Conversational analytics could not write the analysis output files. This might be because of problems with permissions on the output S3 bucket.

Diff

diff --git a/connect/latest/adminguide/contact-lens-error-notifications.md b/connect/latest/adminguide/contact-lens-error-notifications.md
index eed244aa0..588859db5 100644
--- a//connect/latest/adminguide/contact-lens-error-notifications.md
+++ b//connect/latest/adminguide/contact-lens-error-notifications.md
@@ -59,2 +59,2 @@ INVALID_ANALYSIS_CONFIGURATION | Conversational analytics received invalid value
-RECORDING_FILE_CANNOT_BE_READ | Conversational analytics can't get the recording file. This might be because file isn't present in the S3 bucket, or there are problems with permissions.  
-RECORDING_FILE_TOO_SMALL |  The recording file is too small for analysis (less than 105 ms). If file doesn't have expected format, an INVALID error occurs. Empty JSON is also an unexpected object.  
+RECORDING_FILE_CANNOT_BE_READ | Conversational analytics can't read the recording file. This might be because the file isn't present in the S3 bucket, there are problems with permissions, or an error occurred when conversational analytics tried to read the file.  
+RECORDING_FILE_TOO_SMALL |  The recording file is too small for analysis (less than 500 ms). If file doesn't have expected format, an INVALID error occurs. Empty JSON is also an unexpected object.  
@@ -68 +67,0 @@ RECORDING_FILE_INVALID | The recording file is invalid.
-RECORDING_FILE_CANNOT_BE_READ | An error occurred when conversational analytics tried to read the recording file.  
@@ -70,0 +70,3 @@ RECORDING_SAMPLE_RATE_NOT_SUPPORTED | The sample rate of the audio file is not s
+UNSUPPORTED_RECORDING_FORMAT | The format of the recording file is not supported for analysis.  
+ANALYSIS_FILES_CANNOT_BE_WRITTEN | Conversational analytics could not write the analysis output files. This might be because of problems with permissions on the output S3 bucket.  
+MAX_PACKAGE_FEATURE_ONLY | The requested analysis feature is available only for Connect Customer Customer enabled instances.