any ssh traffic that does not look like ssh traffic (few bytes send to server, some more bytes returned) gets either terminated or slowed down to a crawl
If you use fail2ban and asterisk you will probably have to rewrite the asterisk regex rules in fail2ban.
Not a big thing, but it will probably not work out of the box.
A lot of talk about the Apple tax of 30%. But who is actually paying the vat of the purchase price? The developer or apple?
If it is Apple, then with VAT rates of ~20% in the EU, a 30% cut all of a sudden does not sound so unreasonable.
As per your other answer, websocket connections are established just fine
"Now, whenever a new Webhook response comes ... it doesn't have information regarding which instance was used earlier for making the websocket connection, it may send request to one of the instance where the connection was not established and thus our backend is not able to process this request from this particular instance."
just include the internal ip of the websocket connection to the data you send to your billing operator and then forward the post request appropiately.
Easiest way is to check on the client side if the websocket connection is established, if not, just try to reconnect after a couple of seconds.
Maybe there is a problem on the backend that dns is faster than establishing a new instance, so retrying is your best option.
" the connection is not getting established all the time"
Which connection does not get established? The webhook connection to your backend or the websocket connection to your backend?
Or do you get a webhook response, but failing to send a response via websocket?