I have recently setup an EC2 instance (in a VPC with no load balancer) and admittedly the configuration is a bit odd, but it is what is required for the web application we're running.
The web server (in Haskell) is running on port 4433 (standard ports are reserved for an Apache instance) and is receiving UDP packets being broadcast from another system. I have many of the ports wide-open (just during testing) as shown here (from Security Groups):
Custom TCP Rule 4433 tcp 0.0.0.0/0 ✔ Custom TCP Rule 8080 tcp 0.0.0.0/0 ✔ SSH 22 tcp 0.0.0.0/0 ✔ HTTP 80 tcp 0.0.0.0/0 ✔ HTTPS 443 tcp 0.0.0.0/0 ✔ Custom UDP Rule 30090 udp 0.0.0.0/0 ✔ Custom UDP Rule 30089 udp 0.0.0.0/0 ✔
WebSocket connection to 'wss://[URL]:4433/projects/socket' failed: WebSocket opening handshake was canceled.
Binding the socket to 0.0.0.0 results in the same error.
In order to start the Haskell web server I had to reference the internal IP provided by AWS as it would not run when referencing the public IP provided by the elastic IP service. Thinking this is where the problem came in I changed my socket request to this...
This changes the error:
WebSocket connection to 'wss://[internal IP]:4433/projects/socket' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
That error makes sense to me as the internal IP is not available to the outside world.
Everything that I've read on websockets on AWS involves an ELB (Elastic Load Balancer) and I am not in need of one of those. I have tried all of the things in all of the currently posted answers (some of the questions haven't even gotten answers) on SO to no avail. I also setup a support case with Amazon (nearly 24 hours ago) which hasn't received a response.
http://[URL]:4433/projects/socket yields 'WebSocket Available' where the URL is the one we wish to use as well as the Public DNS provided by AWS.
netstat -plunt reveals the following:
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp 0 0 [internal IP]:8080 0.0.0.0:* LISTEN - tcp 0 0 [internal IP]:4433 0.0.0.0:* LISTEN - tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 :::443 :::* LISTEN - tcp6 0 0 :::80 :::* LISTEN - udp 0 0 [internal IP]:30089 0.0.0.0:* - udp 0 0 0.0.0.0:30090 0.0.0.0:* - udp 0 0 0.0.0.0:11950 0.0.0.0:* - udp 0 0 0.0.0.0:68 0.0.0.0:* - udp6 0 0 :::38450 :::* -
Has anyone had a similar problem with websockets on AWS? If so, how did you solve the problem?