SQS endpoint subscription

lukasz.druczak

Hi, we use /alerts/v1/news-stories-subscriptions to create subscription and pull messages from SQS.

We have noticed that our sqs endpoint always ends up being https://sqs.us-east-1.amazonaws.com.

Is this something that we can control? I mean can we configure what endpoint we pull messages from?

Find more posts tagged with

news

rdp-api

#technology

Accepted answers

wasin.w

Hello @lukasz.druczak

I checked with the News Alert team. The team confirms that the API has only one region server which is AWS us-east-1.

I hope this information helps.

All comments

wasin.w

Hello @lukasz.druczak

I checked with the News Alert team. The team confirms that the API has only one region server which is AWS us-east-1.

I hope this information helps.

lukasz.druczak

Hi, that is clear thanks!

lukasz.druczak

Hi, @wasin.w ,

We have just noticed that when we are creating a subscription, there are multiple platform streaming endpoints that can be used. Our service is located in the UK, why do we end up in the us-east?

wasin.w

Hello @lukasz.druczak

Please be informed that the accepted question will not be monitored. I strongly suggest you create a new question next time.

About how to set the streaming price/RTO region with the Data Library, please check my colleague answer on this How can I assign a specific region of RTO in Data Labrary? old post.

I did a quick test with the Data Library version 1.6.2 and LSEG Data Library (aka Data Library version 2.0.0) on the EX-2.02.04-Pricing-StreamingEvents.ipynb example. It connects to the EU endpoint as my configuration file.

Config file:

{
    "apis": {
    "streaming": {
      "pricing": {
        "endpoints": {
          "main": {
            "locations": [
              "eu"
            ]
          }
        }
      }
    }
  },
    "logs": {
...

Result:

    config : PlatformStreamCxnConfig
        headers=[],data_formats=['tr_json2'],supported_protocols=['OMM'],data_fmt=tr_json2
        urls : wss://eu-central-1-aws-1-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
               wss://eu-central-1-aws-3-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
               wss://eu-central-1-aws-2-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
               wss://eu-west-1-aws-1-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
               wss://eu-west-1-aws-3-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
               wss://eu-west-1-aws-2-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
[2024-09-05T19:37:27.780797+07:00] - [sessions.platform.ldp.0] - [DEBUG] - [27380 - OpenUniverseStreams-Thread_0] - [_stream_cxn_cache] - [get_cxn] -  + StreamCxnCache created new connection: id=0, daemon=False, content_type=ContentType.STREAMING_PRICING, protocol_type=ProtocolType.OMM
[2024-09-05T19:37:27.780797+07:00] - [sessions.platform.ldp.0] - [DEBUG] - [4680 - ThreadOMMSTREAMING_PRICING_0.0] - [stream_connection] - [run] - [OMMSTREAMING_PRICING_0.0] wait start connecting
[2024-09-05T19:37:27.780797+07:00] - [sessions.platform.ldp.0] - [DEBUG] - [27380 - OpenUniverseStreams-Thread_0] - [_stream_cxn_cache] - [get_cxn] - StreamCxnCache wait for connection: id=0, content_type=ContentType.STREAMING_PRICING, protocol_type=ProtocolType.OMM
[2024-09-05T19:37:27.780797+07:00] - [sessions.platform.ldp.0] - [DEBUG] - [4680 - ThreadOMMSTREAMING_PRICING_0.0] - [stream_connection] - [run] - [OMMSTREAMING_PRICING_0.0] is connecting
[2024-09-05T19:37:27.780797+07:00] - [sessions.platform.ldp.0] - [DEBUG] - [4680 - ThreadOMMSTREAMING_PRICING_0.0] - [stream_connection] - [_run_websocket_listener] - [OMMSTREAMING_PRICING_0.0] connect
    num_attempt : 0
    url         : wss://eu-central-1-aws-1-lrg.optimized-pricing-api.refinitiv.net:443/WebSocket
    headers     : ['User-Agent: Python']
    cookies     : None
    transport   : websocket
    subprotocols: ['tr_json2']

EXPLORE OUR SITES