Server Infrastructure - HTTPS for dynamic servers

[reececomo]

Hey 👋

Re: spinning up dynamic servers in production:

• We have a central server that is responsible for discovery/matchmaking:
  • Gameservers auto-scale and notify the central API when they come online.
  • Users request a game, and the server responds with an address.

POST https://api.mywebsite.com/matchmaking/find-game

{
  "gameserver": {
    "id": "f2ce56ae-9521-41b0-9cab-a429a0e27288",
    "address": "123.123.123.123:9208",
    "region": "antarctica",
    "gameVersion": "93e167e91c800a5acfc04af90e320422"
  }
}

^ Simplified version for illustrative purposes

What is the happy-path for connecting to dynamic servers over HTTPS?

• ❌ Connect directly to the IP over HTTP fails with Mixed Content: [...] This request has been blocked; the content must be served over HTTPS.
• ❌ Connect directly to the IP over HTTPS with self-signed certificate fails with NET::ERR_CERT_AUTHORITY_INVALID
• Generate dynamic DNS entries for each gameserver? https://gameserver-123-123-123-123-9208.connect.mywebsite.com
• Custom load balancer to handle SSL offloading and parses the IP/server ID from the request?
• Something even simpler?

---

If anyone has any practical examples to share, would love to take a look.

edit: For context we're currently using AWS, but flexible on infra. Considering using K8s/Agones, but that appears to face the same problem -> browsers can't connect to the webrtc signalling server without HTTPS.