Unable to connect to websocket gateway on a NestJS Application deployed via App Runner
I implemented a simple websocket gateway on a NestJS application and it successfully connects when deployed locally but when deployed on AWS App Runner, it returns a 403 error. See image attached.
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
There are several possible causes of a 403 error that may appear when attempting to connect to a WebSocket gateway in a NestJS application that has been set up on AWS App Runner. To troubleshoot and fix the issue, follow these steps:
Verify Network Configuration and Security Groups: Make sure that the WebSocket port that you have defined for incoming traffic is open in the security groups linked to your App Runner service. Make sure that no firewalls or network ACLs (access control lists) are preventing WebSocket connections.
Check WebSocket Endpoint: Make that the URL you are using to connect to the WebSocket endpoint corresponds to the settings of your deployed application.
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 3 anni fa
Hi Ronald, Thanks for the answer but I cant find where the Network Configuration and security groups settings are on the console. Could you guide me through on how to access them?