LPC Usage with AWS Privatelink

For customers migrating from EZD to Realtime Optimized via Legacy Protocol Converter (LPC), is it possible to use LPC through AWS PrivateLink? After viewing the LPC installation guide on DevComm, I did not see any step to configure the access endpoint or URL which would need to be customized to work with PrivateLink. Is LPC only compatible with standard Internet connectivity?

Find more posts tagged with

elektron

elektron-sdk

refinitiv-realtime

Accepted answers

christopher.dugan1

Section 4.4 of the Refinitiv Real-Time Legacy Protocol Converter 1.2 shows how to configure RRTLPC for AWS Private Link. To actually implement Private Link to the Refinitv Real-Time service, you must follow the procedures in the Refinitiv Real-Time Cloud document.

All comments

nicolas.ooka

One more follow up question if I may. Customer also wants to confirm if the client application connecting to the LPC can designate a hostname rather than a specific IP address to connect to the LPC process. I would assume that provided the application has the ability to resolve the hostname to an IP address that a hostname would also be possible. Thanks again!

umer.nalla

Hi @nicolas.ooka

AFAIK name resolution etc is a function of the OS - rather than the API / application etc.

I run the LPC converter on my Windows PC and if I want to consume data from it using one of our APIs, I can set the Host parameter in the API config to any of the following and it works

localhost
127.0.0.1
PC-AB1234567 (assuming this is my actual PC hostname)

nicolas.ooka

Thanks again @umer.nalla

Yes, I would expect that as long as the system the application is running on is capable of normal name resolution that using a hostname instead of an IP address should work fine.

christopher.dugan1

nicolas.ooka

Thanks so much @christopher.dugan1! I must have been looking at the older v1.1 of the installation manual. Very glad to know that AWS PrivateLink can work with LPC!

EXPLORE OUR SITES