Sandbox-Dallas Onboarding Guide
This topic describes client onboarding and setup services for those who choose to participate in the new CME Globex on Google Cloud Sandbox-Dallas (Sandbox-Dallas) environment, which is located in the private Ultra Low Latency zones of the Google Cloud Dallas Region.
Contents
- 1 Revision History
- 2 Getting Started with Sandbox-Dallas
- 3 Sandbox-Dallas Setup Overview
- 4 Sandbox-Dallas Setup Details
- 5 Support Contact Details
Revision History
Date | Description |
|---|---|
July 9, 2026 |
|
June 15, 2026 | Added url for new Sandbox instance of the Request Center. |
June 12, 2026 | Added Sandbox-Dallas Multicast Resource Paths, Network Configuration Details and NCC Hub Reference Points , API testing requirements and Sandbox testing support. |
May 7, 2026 | Initial publication of this client impact topic. |
Getting Started with Sandbox-Dallas
Client onboarding is a partnership between clients, CME Group and Google Cloud.
For an overview of the Sandbox-Dallas environment and if you are new to CME Globex on Google Cloud or wish to better understand the detailed scope for client testing, please refer to the Client Systems Wiki.
For comprehensive Sandbox-Dallas validation details, see the Production Readiness Framework topic.
Sandbox-Dallas Setup Process
To access and participate in the Sandbox-Dallas environment, clients must complete a structured onboarding workflow.
Sandbox-Dallas Setup Overview
Use the following checklist to track required activities to access and set up Sandbox-Dallas.
Required Setup Steps | Additional Details |
|---|---|
Use an existing CME Group Login ID or create a new CME Group Login with multi-factor authentication. Set up Duo multi-factor authentication.
| CME Group Login and Duo multi-factor authentication is required to access forms, services, applications, and for viewing premium website content. All clients who access CME applications must have a unique CME Group Login ID. Designated persons and application users can request access from their entity administrator. To complete application access, users provide their existing CME Group Login ID and secure token to the entity administrator to complete setup. CME Group or entity administrators will never ask for your password. |
Complete and sign the Google Master Service Agreement (MSA) form. | Confirm that an existing relationship with Google is established. If not, Global Account Management (GAM) can provide a Google contact. |
Complete and sign the Customer Connection Agreement (CCA) and the Self-Service Agreement (SSA) forms. | GAM confirms with the customer if they have CME agreements in place. |
Complete CME Globex Sandbox-Dallas Testing Setup. | Refer to the CME Globex Sandbox-Dallas Testing Setup. Users must contact GAM to request front office admin access to the CME Request Center Sandbox, which is used to create and view requests for Globex Firm IDs (GFIDs) for API testing. |
To request access to CME Group APIs (iLink Order Entry, Drop Copy, Market Data, Reference Data API), contact GAM. | |
Access Sandbox-Dallas Environment Self-Service functions via CME Request Center to manage Sandbox-Dallas environment configuration. | Create GFID, iLink session IDs and Drop Copy sessions. |
Setup MDP 3.0 via Hardware Multicast or MDP 3.0 via Cloud Multicast as required. | For questions or issues, contact GAM. |
Sandbox-Dallas Setup Details
The following sections provide additional details about setting up and accessing Sandbox-Dallas, as described in the checklist above.
Prerequisite for Sandbox-Dallas Access Models
Before onboarding to access CME Globex markets on Google Cloud, all clients who want to test in the Sandbox-Dallas environment must contact GAM.
CME GAM Validation
GAM will verify a client’s eligibility as a valid CME Globex customer. All clients must have completed the existing CME Group trading entity onboarding. Firms must confirm the entity name on their existing CME agreements, which must include a Customer Connection Agreement (or Data Center Connection Agreement) and a Self-Service Agreement.
If a client attempts to contact Google before completing this initial step, Google will automatically route them back to GAM.
Firms need to identify a “Sandbox Admin” with GAM.
Engage with Google Cloud
GAM will confirm if a client already has a relationship and agreement with Google. If not, GAM will provide the client with a Google contact.
Any clients who want to use the Google Cloud ULL Compute Engine instances (Bare Metal U4C and Virtual Machine U4S) must have completed the Google Cloud Master Services Agreement.
GAM will ensure client uses the same entity name for both Customer Connection Agreement (CCA) and the Google Cloud Master Services Agreement.
Clients must obtain unique Google Project ID(s) and confirm their Google Organization Name (Domain) and Google Organization ID.
These prerequisites are independent and can be completed in any order or in parallel.
Clients must complete all prerequisites before requesting access to Globex on Google Cloud.
Client Setup for Sandbox-Dallas
The new CME Request Center Sandbox service is used to manage requests for Sandbox-Dallas connectivity and market access for testing. To begin testing in the Sandbox-Dallas environment, clients must complete the following requirements:
New Clients: New users of the CME Request Center-ESS should contact their GAM to get started.
Connectivity
Starting in June, clients can log in to CME Request Center-ESS Sandbox using a CME Group Login.
Register Google Customer Information:
Google Organization Name (Domain)
Google Organization ID (12-digits numeric ID assigned by Google)
Google Project ID (Unique Identifier created by customer)
Google Project Number (Numeric ID from Google Cloud)
Google Cloud Identity (Account requesting the network connection)