AWS connect documentation change
Summary
Added troubleshooting for file type rejection issues, expanded scope to include task channel attachments, updated CORS policy step reference, and added information about configurable attachment size limits up to 100 MB.
Security assessment
The changes are routine documentation updates about attachment functionality and troubleshooting. No security vulnerabilities, incidents, or weaknesses are mentioned. The changes focus on operational guidance for file type validation and size limits, which are normal configuration parameters.
Diff
diff --git a/connect/latest/adminguide/ts-agent-attachments.md b/connect/latest/adminguide/ts-agent-attachments.md index 760bb9d20..671efe8d2 100644 --- a//connect/latest/adminguide/ts-agent-attachments.md +++ b//connect/latest/adminguide/ts-agent-attachments.md @@ -7 +7 @@ -Configure a CORS policy on your attachments bucketInternal firewall settings are preventing accessAttachments are too large, too many, or don't meet file type requirements +Configure a CORS policy on your attachments bucketInternal firewall settings are preventing accessAttachments are too large, too many, or don't meet file type requirementsFile type is rejected even though it is expected to be allowed @@ -9 +9 @@ Configure a CORS policy on your attachments bucketInternal firewall settings are -# Internal firewall or missing CORS policy prevents access to chat, email, or case attachments +# Internal firewall or missing CORS policy prevents access to chat, email, task, or case attachments @@ -11 +11 @@ Configure a CORS policy on your attachments bucketInternal firewall settings are -This topic is for developers who need to investigate issues that may occur when using attachments with the chat or email channels in Amazon Connect, or when using attachments to upload files to cases. +This topic is for developers who need to investigate issues that may occur when using attachments with the chat, email, or task channels in Amazon Connect, or when using attachments to upload files to cases. @@ -13 +13 @@ This topic is for developers who need to investigate issues that may occur when -The following issues may cause attachments to not display for your agents using Amazon Connect chat or email, or Amazon Connect Cases. +The following issues may cause attachments to not display for your agents using Amazon Connect chat, email, or tasks, or Amazon Connect Cases. @@ -17 +17 @@ The following issues may cause attachments to not display for your agents using -A common reason for attachments not appearing in chats or emails is that the CORS policy hasn't been configured on your attachments bucket. For instructions, see [Step 2: Configure a CORS policy on your attachments bucket](./enable-attachments.html#step2-update-cors-policy). +A common reason for attachments not appearing in chats, emails, or tasks is that the CORS policy hasn't been configured on your attachments bucket. For instructions, see [Step 3: Configure a CORS policy on your attachments bucket](./enable-attachments.html#step3-update-cors-policy). @@ -26,0 +27,2 @@ Check that the attachments meet the size, number, and file type requirements. Fo +The maximum attachment size is configurable up to 100 MB. The default is 20 MB. If attachments are being rejected, verify the configured size limit for your instance through the Amazon Connect admin website or the Amazon Connect API. + @@ -28,0 +31,6 @@ To calculate the size of an attachment (artifactSizeInBytes), use a third-party +## File type is rejected even though it is expected to be allowed + +If a file type is rejected when uploading an attachment, verify that the file extension has been added to the allowed file extensions list for your instance. For information about configuring custom file extensions, see [Enable attachments in your CCP so customers and agents can share and upload files](./enable-attachments.html). + +For a list of default supported file types, see [Amazon Connect feature specifications](./feature-limits.html). +