Service discovery Private Link, AWS Direct Connect and Delivery Direct
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 ?
Best Answer
-
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
1
Answers
-
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 CommunityThe 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/0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛