Hi all, We're deploying Edge Processor on Kubernetes using the official Helm chart and Docker, and hitting a consistent OpAMP registration failure on all new groups we create. Setup steps: 1. Create a new Edge Processor group in SCS UI 2. Run `eptools setup` with a fresh token — succeeds, generates principal.yaml with valid servicePrincipalId 3. Run the EP container with the principal mounted What works: - Token validation: HTTP 200 from /identity/v3/validate - Auth token exchange: HTTP 200 from auth.scs.splunk.com What fails: - OpAMP registration returns HTTP 500 via user token path - OpAMP registration returns HTTP 403 via token signer (principal) path Full error: Error: failed to register agent with opamp: failed to register agent with scs (id: , groupId: ) using both user token (error: failed to register with OpAMP (status code: 500)) and token signer (error: failed to register with OpAMP (status code: 403)) What we've tried: - Tested with both splunk/edge-processor:1.0.0 and 1.0.3 - Created multiple brand-new groups — all fail the same way - Reproduced locally with Docker using the exact install commands from the SCS UI (px.scs.splunk.com) - Reproduced on EKS Kubernetes with the official Helm chart - Deleted all resources and reinstalled from scratch - Verified system clock is correct (NTP synced) Environment: - Region: iad10 - Splunk Cloud Platform (Premium) - Kubernetes 1.30 (EKS) and local Docker Desktop This feels like a service-side issue since authentication succeeds but the OpAMP endpoint rejects registration. We noticed a "Cloud Region Network Connectivity" incident on May 10 on the status page — could that still be affecting OpAMP/agent-management services? Has anyone else experienced this or have a workaround? Thanks in advance. ... View more