For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
Which request I have to make if I want to do a service discovery ( streaming pricing end points) if I connect through:
1. AWS Private Link
2. AWS Direct Connect
3. Delivery Direct
Does the service discovery requests has to be made over the internet ?
Hi @wo ,
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.
Thanks,
AHS
Hi @wo ,
These are excellent questions- let me try to address them.
Refinitiv Real-Time - Optimized Install and Config Guide contains much of the relevant details on this subject for developers.
For AWS Private Link integration, service discovery is recommended, refer to section Using Service Discovery for PrivateLinks:
"...This release introduces several optional boolean parameters (listed on the following table), with the only expected value being true.
For example:
$service-discovery-url/streaming/pricing/v1?transport=tcp&dataformat=rwf&privatelink=true&tier=true&locationid=true
"
I believe for service discovery with Delivery Direct connectivity option, the same discovery endpoint https://api.refinitiv.com/streaming/pricing/v1 should be used in the same way, but for the streaming pricing, the next step, it may require additional network whitelistings, that are described in section Using AWS PrivateLink-> Firewall Whitelisting
Service discovery is a discrete request response that goes over the internet. I could not find the description of any other usage in the configuration guide. Because the alternative option for Private Link is not included in the guide, and because Private link requests require being in the same availability zone with the streaming pricing endpoints- please see configuration diagram in AWS PrivateLink Access Configuration- I believe this to be the only option.
Additionally, a client should have an Refinitiv Real-time Optimized email welcome letter, with the details pertaining to their connectivity option, user id and instructions for the next steps, prior to configuring and testing the RTO connections, and if a specific issue or a specific concern with the local configuration comes up, the best approach is to engage with RTO support directly to verify the issue.
Hope that this information is of help
Hi all,
Updated information.
For Service Discovery when using Delivery Direct - you will also need to use regional .biz endpoints
The following post lists the correct regional .biz URL Prefixes for Authentication:
Delivery Direct private comms line equivalent for "api.refinitiv.com" - Forum | Refinitiv Developer Community
The same regional prefixes will be required for service discovery as well i.e.
https://us-east-1-api.refinitiv.biz/streaming/pricing/v1/
https://eu-west-1-api.refinitiv.biz/streaming/pricing/v1/
https://ap-southeast-1-api.refinitiv.biz/streaming/pricing/v1/
