Does anyone know… if there are specific TLS handshake requirements for the Genesys Cloud BYOC edge proxy when handling large payload bulk export jobs for legal discovery? We are operating in the Europe/London region and have configured a custom edge proxy for our Bring Your Own Container (BYOC) deployment to manage data residency compliance. The standard digital channel recording exports via S3 integration were functioning correctly until the last maintenance window on the 14th. Now, when initiating a bulk export job for Web Chat transcripts using POST /api/v2/analytics/conversations/export, the job status transitions to ‘failed’ almost immediately. The error log in the Genesys Cloud admin console indicates a 502 Bad Gateway error originating from the edge proxy layer, specifically citing a timeout during the initial metadata handshake with the S3 bucket. We have verified that the IAM policies for the S3 bucket are correct and that the network connectivity between the BYOC container and the S3 endpoint is stable. The issue seems isolated to the export of digital channel metadata, as voice recording exports to the same bucket proceed without interruption. We are running Genesys Cloud version 2024.07.1 and the BYOC container version is 1.2.4. The edge proxy logs show a repeated ‘connection reset by peer’ error when the export job attempts to stream the manifest.json file. This is critical as we have pending legal hold requests that require immediate data extraction. We have checked the edge proxy configuration for any recent certificate updates, but nothing appears to have changed. The metadata fields for chat_id and participant_uri are present in the request payload, yet the proxy rejects the connection before the data transfer begins. Any insights into potential edge proxy configuration conflicts with the bulk export API for digital channels would be greatly appreciated.