BYOC Edge Gateway TLS Handshake Failure with Custom Cert

No idea why this is happening, the Genesys Cloud BYOC edge gateway fails to establish a secure connection with our private AWS ALB. The deployment is automated via Terraform provider v1.98.0. The error log on the Genesys side shows TLS handshake timeout after 30s. Our ALB uses a custom ACM certificate chain. Verified the cert is valid and trusted via curl -v. The genesyscloud_edge_gateway resource applies successfully, but health checks fail immediately.

resource "genesyscloud_edge_gateway" "private_edge" {
 name = "prod-private-edge"
 description = "Private edge for BYOC"
 type = "VIRTUAL"
 # ... config omitted for brevity
}

The issue seems specific to the TLS 1.3 negotiation. Genesys edge expects specific cipher suites. Checking the genesyscloud_edge_gateway documentation, there is no explicit attribute to force TLS 1.2 or specify cipher suites. The ALB is configured to accept TLS 1.2 and 1.3. Is there a hidden configuration parameter or API endpoint to debug the exact cipher mismatch? The logs only show the timeout, not the specific handshake failure reason. Need to resolve this before the next release window. Any insights on debugging BYOC edge TLS issues?

Have you tried checking if the intermediate certificates are included in the ALB listener configuration, as missing intermediates often cause handshake timeouts even if the leaf cert is valid?

Note: Ensure the chain order is correct (leaf first).