Sadly, AWS Api Gateway does not support Socket.io

[c0j0s]

See this

We might need to migrate to the WebSocket protocol instead.
or we could expose matching-service ecs to public access, but this is cumbersome as we will be dealing with dynamic IP addresses for connection.

I'll migrate matching-service first to evaluate the effort needed before we make any final decision.

[weidak]

Have you seen http-proxy? Not sure if this will work:

https://socket.io/docs/v3/reverse-proxy/

There are multiple posts stating it is possible to expose the server through API gateway, just that i cant find a solution... (like this in point 2. socketio/socket.io-client#1370 (comment))

Configuring HTTP proxy:
https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-http.html

[c0j0s]

Sure, I'll try http-proxy out first

[c0j0s]

Seems like aws proxy path works with socket.io in polling mode, so no major change is required. 🙂