This topic describes client impacts for CME STP FIX API on Google Cloud.
...
Clients who are on one of the specific Production Connectivity Options offered by CME Group can use CME STP FIX on their connectivity option using the below server destinations.
If clients cannot use a public DNS on their side, they should deploy a local DNS override (i.e. host-file entry). This will ensure that the server certificate name will match up with client requests and they can rely on standard certificate validation.
Connectivity Type | Asset Class | New Service URL (GC) - Region-a | New Service URL (GC) - Region-a | Usage | Port |
|---|---|---|---|---|---|
Dedicated connectivity - Futures and Options clients | All | stpfix-ll-fo-a.api.cmegroup.com (208.112.160.2) | stpfix-ll-fo-b.api.cmegroup.com (208.112.144.2) | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. | 443 |
Dedicated connectivity - BrokerTec FI clients | All | stpfix-ll-btec-a.api.cmegroup.com (208.112.164.2) | stpfix-ll-btec-b.api.cmegroup.com (208.112.148.2) | ||
Dedicated connectivity - EBS FX clients | All | stpfix-ll-ebs-a.api.cmegroup.com (208.112.168.2) | stpfix-ll-ebs-b.api.cmegroup.com (208.112.152.2) |
Service URL's use certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.
...
There will be no changes to the CME STP FIX server and client message payload.
Automatic TCP/IP Disconnection
...