Edge BYOC Setup Failing with 401 Unauthorized During Zendesk Migration Pilot

Is it possible to use the Genesys Cloud Edge BYOC feature to host our on-premise infrastructure while migrating from Zendesk? We are in the middle of a complex migration from Zendesk to Genesys Cloud and decided to try the Bring Your Own Cloud option to keep our sensitive data processing within our own AWS VPC, similar to how Zendesk handled our private deployment. The goal is to maintain the same level of control we had with Zendesk’s private instance while leveraging Genesys Cloud’s routing. I have followed the documentation for setting up the Edge cluster, using the provided Terraform scripts. The cluster appears to be running, and the health check endpoints return 200 OK. However, when I try to register the Edge cluster with the Genesys Cloud tenant using the POST /api/v2/edge/clusters endpoint, I consistently get a 401 Unauthorized error. The error message states: “Invalid or expired access token.” I have double-checked the API credentials and ensured that the user has the admin:edge permission set. The timezone for our deployment is Europe/Paris, and we are using the eu-west-1 region. I have also tried regenerating the API keys, but the issue persists. In Zendesk, we used a simple token-based authentication for our private instance, so I assumed Genesys Cloud would be similar. Is there a specific step I am missing in the Edge registration process? Could this be related to the VPC peering configuration or the IAM roles assigned to the Edge instances? I have checked the logs on the Edge cluster, and they show that the authentication request is being sent correctly, but Genesys Cloud is rejecting it. Any help would be appreciated as we are on a tight deadline for this migration. We want to ensure that the Edge setup is robust before we move all our agents over from Zendesk.