A real-time messaging application uses Amazon API Gateway WebSocket APIs with backend HTTP service.

Requirement Summary:

WebSocket-based messaging app usingAPI Gateway WebSocket APIs

Need to:

Identify clients repeatedlyconnecting/disconnecting

Be able toremoveproblematic clients

Evaluate Options:

A. Switch to HTTP APIs

❌HTTP APIs don’t supportWebSocketconnections

B. Switch to REST APIs

❌REST APIs arenot compatiblewith WebSockets

✅C. Use the callback URL to disconnect clients

⚠️Possible, butnot a direct option

Callback URLs are used forsending messages to connected clients, not for disconnecting

✅D. Track client status in ElastiCache

✅Good solution: Store and update connection state (connected, disconnected, timestamps)

Helpstrack abuse or reconnections

✅E. Implement $connect and $disconnect routes

✅Required to captureconnection lifecycle events

These can be used to log/store client behavior and decide on removal

WebSocket routes in API Gateway:https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-route-selection.html

Managing WebSocket connections:https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-mapping-template-reference.html