EMA AWS endpoints and ports in service discovery and session management

Frederic

3 questions, for the RTO / Real-Time in the Cloud, in the scenario of network firewall,

1. Can we make assumption the following AWS endpoints will not be changed? and there will be a PCN notification sent out if those endpoints will be changed by plan?

2. To subscribe the CME (Chicago) data, and the application basically will be running in Asia/China, how to choose which region is the best in the consideration of network latency?

3. If we enable the session management mode in the EmaConfig.xml and specify the 'location' config item based on the answer of question 2, will the EMA API underlying try the endpoints of the specified region one by one in case of connection failure?

Thanks.

------------------------------------------------------------------

Services :

Service :

Provider : aws

Transport : tcp

Endpoint : ap-southeast-1-aws-1-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : ap-southeast-1a

Service :

Provider : aws

Transport : tcp

Endpoint : ap-southeast-1-aws-3-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : ap-southeast-1a ap-southeast-1b

Service :

Provider : aws

Transport : tcp

Endpoint : ap-southeast-1-aws-2-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : ap-southeast-1b

Service :

Provider : aws

Transport : tcp

Endpoint : eu-west-1-aws-1-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : eu-west-1a

Service :

Provider : aws

Transport : tcp

Endpoint : eu-west-1-aws-3-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : eu-west-1a eu-west-1b

Service :

Provider : aws

Transport : tcp

Endpoint : eu-west-1-aws-2-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : eu-west-1b

Service :

Provider : aws

Transport : tcp

Endpoint : amer-1-t2.streaming-pricing-api.refinitiv.com

Port : 14002

Data Format : rwf

Location : us-east-1a

Service :

Provider : aws

Transport : tcp

Endpoint : amer-3-t2.streaming-pricing-api.refinitiv.com

Port : 14002

Data Format : rwf

Location : us-east-1a us-east-1b

Service :

Provider : aws

Transport : tcp

Endpoint : amer-2-t2.streaming-pricing-api.refinitiv.com

Port : 14002

Data Format : rwf

Location : us-east-1b

Service :

Provider : aws

Transport : tcp

Endpoint : us-east-2-aws-1-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : us-east-2a

Service :

Provider : aws

Transport : tcp

Endpoint : us-east-2-aws-3-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : us-east-2a us-east-2b

Service :

Provider : aws

Transport : tcp

Endpoint : us-east-2-aws-2-med.optimized-pricing-api.refinitiv.net

Port : 14002

Data Format : rwf

Location : us-east-2b

umer.nalla

Hi @Frederic

1. There are no plans for change in the near future. If changes are planned, then PCN or similar will be issued. Customer should ensure they register for the relevant alerts at My.Refinitiv
2. If the application is running in China, AP-SOUTHEAST makes most sense for the region - but I will ask for confirmation from the RTO Team
3. EMA will attempt with different endpoints in case of failure

The customer can also use ChannelSets with different locations in each Channel config to benefit from cross-regional resiliency. See section on ChannelSets in my article Enterprise Message API (EMA) - Configuration Overview | Refinitiv Developers