Changing from TCP to TLS for AWS

weishengtay · 2025-01-06T09:12:33+00:00

There was an error rendering this rich post.

Hi, we would like to check if ads pop in the AWS environment supports TLS listener port such as port 14002 and including the ads & dacs related ports.

If yes, is there a guide on how we can configure to get the hub to get the route connected to the feed

Find more posts tagged with

trep

ADH

aws

#technology

RTO

Accepted answers

All comments

wasin.w

Hello @weishengtay

About the ADS Pop in the AWS, do you mean the Real-Time Optimized (RTO)?

If so, the RTO currently supports TLS on the RSSL port 14002 and WebSocket port 443.

Please see more detail on the Real-Time - Optimized Install and Config Guide.

About the ADH configurations to connect to RTO, please check section 19.19 Connectivity to Refinitiv Real-Time – Optimized of the ADH SYSTEM ADMINISTRATION MANUAL document in the ADH package.

weishengtay

Hi, you are right we are refering to Real Time Optimized. From the Feed layer to LSEG RTO (we are using encrypted and TLS) this is working.

However, when we changed the Hub layer that is connecting to Feed layer, by changing the listener port in AWS to TLS, there is connection issue which result to the route that is attempting to connect

wasin.w

Hello @weishengtay

If your hub layer is the LSEG Real-Time Advanced Distribution Hub (ADH) and your ADH cannot connect to the RTO feed, I strongly suggest you contact the ADH support team directly via https://myaccount.lseg.com/en/productsupport website.

EXPLORE OUR SITES