Can anyone clarify the specific TLS handshake requirements for our BYOC edge proxy when initiating bulk export jobs for legal discovery? We are operating in the Europe/London region and recently updated our edge certificates to enforce TLS 1.3 only. Since the update, POST requests to /api/v2/analytics/conversations/export fail with a 502 Bad Gateway error returned by the edge proxy before Genesys Cloud processes the payload. The request body includes standard filters for digital channel voice recordings with legal_hold flags set to true.
Our internal logs show the connection is established, but the proxy drops the request during the initial TLS negotiation phase. The Genesys Cloud API documentation mentions support for TLS 1.2 and 1.3, but does not specify if the export service has strict cipher suite requirements that might conflict with our current configuration. We are using the standard v2 API endpoints and have verified that other read-only endpoints work correctly over the same edge path.
Is there a known compatibility issue between TLS 1.3 enforcement on BYOC edges and the bulk export service for legal hold data?