Real-Time - Optimized: Change in Service Discovery Request for WebSocket API - Ticket 13104

Hi @pradeep.badoni

Did you change the value of your location (_region) according to the instructions, i.e.

"Some example WebSocket code have been using the location variable as ‘amers’ or ‘emea’. This should be changed to specify an AWS region such as “us-east-1” or “eu-west-1”."

Hi @pradeep.badoni

If you look at the list of streaming endpoints, you can see they have changed since you first adopted the initial algorithm. For example, there are 3 new ones (us-east-2a, ..., us-east-2b).. There is nothing stopping the streaming services team to add new ones. The current algorthim for selection will likely choose the same streaming endpoint, which would put most users on the same service as opposed to distributing the load.

The algorithm is a guide - not a hardcoded requirement. You can still choose the endpoint based on your hardcoded regions, but you will have to change your algorithm to choose an appropriate one. As I mentioned above, the notification is recommending you choose your endpoint based on a more granular region, not 'amers', 'apac', 'emea' because you will likely always choose the same one from each region. While 'apac' and 'emea' presently have 3 to choose from, this could grow. I would suggest that your drop-down be dynamically created based on discovery as opposed to hard-coding. This way, you can have the complete list available for users.