Regions and clusters
The DeepAffex Cloud API is internationally accessible, as a network connected mesh of distributed AWS clusters, each of which is hosted within a specific geographic region of the globe.
Within mainland China, the DeepAffex Cloud API operates as a standalone network service, that is excluded from the international network. It is a separate deployment on AWS China that operates entirely within China to service the China market exclusively. This deployment is completely isolated from the global DeepAffex Cloud network — there is no mesh connectivity, no cross-routing, and no data exchange between the China deployment and any other global cluster.
All data processing and (optional) storage for the China cluster remain within mainland China.
Both the routing of customer traffic and the processing/storage of measurement results for
the China deployment occur on the cn-north cluster hosted entirely within mainland China.
Clusters
Each distinct DeepAffex cluster provides coverage across a designated region. This regional partitioning of service operates according to defined continent-based geolocation rules that use AWS's DNS Traffic Policy Lookup to manage all IP routing of the originating connection to the destination DeepAffex endpoint. The table below summarizes the rules.
Geographic location and associated routing rules
| Rule name | Cluster name | Cluster location | Used by region | Comment |
|---|---|---|---|---|
Default | na-east | North America (Northern Virginia, USA) | North America, Africa, Australia, Antarctica | The default rule applied when none of the others apply |
Europe | eu-central | Europe (Frankfurt, Germany) | Europe, Saudi Arabia | For Saudi Arabia, overrides Asia rule |
South America | sa-east | South America (Sao Paulo, Brazil) | South America | |
Asia | as-east | Asia (Tokyo, Japan) | Asia | Except Saudi Arabia |
Geographic location and associated routing rules (China)
| Rule name | Cluster name | Cluster location | Used by region | Comment |
|---|---|---|---|---|
China | cn-north | Mainland China (Beijing, China) | Mainland China | Only used by Mainland China |
Routing Options
Two routing options are available to NuraLogix integration partners who have licensed access to the DeepAffex API.
The details of both these options follow.
The mainland China deployment is a standalone environment, completely separate from the global DeepAffex Cloud and excluded from the connected mesh. The routing rules described below do not apply to it.
If you intend to use the DeepAffex Cloud API in mainland China, you should use
the China cluster by replacing deepaffex.ai with deepaffex.cn in the URLs
mentioned on this page. e.g. https://api.deepaffex.cn,
https://dashboard.deepaffex.cn/ etc.
You will need to obtain separate licenses for DeepAffex Cloud API in China. All
data processing and results storage for China happens exclusively within China
on the cn-north cluster, and that data never leaves China.
Option #1: Default Routing (no region locking)
With this option, you would use the global URL:
https://api.deepaffex.ai for all network calls to the DeepAffex Cloud API.
Network traffic from each edge device will be routed to the cluster determined
using the routing rules described
in the table above.
-
Data processing: Data will be processed by the cluster determined by the routing rules.
-
Results storage: If your DeepAffex ORG is configured to store results, they will be stored in the cluster-name encoded in the active Device Token. This is the cluster that was used to obtain the token by registering a license.
Under default routing, the cluster that processes a measurement (chosen by the
geolocation routing rules, based on where the device connects from) is not
necessarily the cluster that stores the results (fixed by the cluster encoded
in your Device Token at license registration). For example, a device that
registered its license against na-east but operates in Europe will be
processed by eu-central while its results are stored in na-east. If you need
processing and storage to occur in the same region, use
Region Locking.
Note: The purpose of the default routing rules is to manage regional requirements for data localization and processing of customer traffic with the DeepAffex Cloud. It's important to recognize that these requirements are often contradictory, imprecise and lack consistency between customers so these routing rules may not satisfy all use-cases. If this default behaviour isn't desirable, please see the Region Locking alternative below.
URLs Where Routing Rules Are Applied
| Service | Routing URL |
|---|---|
| DeepAffex API | https://api.deepaffex.ai |
| DeepAffex Dashboard | https://dashboard.deepaffex.ai |
| Anura Web Enterprise / Web Measurement Service | https://awe.nuralogix.ai |
Checking Which Rules Apply To You
It's possible to check in advance which region your device will be routed to by calling the following endpoint:
curl https://api.deepaffex.ai/status
You may also visit https://api.deepaffex.ai/status in a browser from the region you want to check.
The response, will contain the "Region" field:
{ ..., "Region":"na-east" }
If you want to check a different location, you may need to use a VPN.
Examples
Some examples of territories and the clusters they resolve to:
| Origin | Rule applied | Resolves to cluster |
|---|---|---|
| Australia | Default | na-east (Virginia, USA) |
| Canada | Default | na-east (Virginia, USA) |
| Colombia | South America | sa-east (Sao Paulo, Brazil) |
| India | Asia | as-east (Tokyo, Asia) |
| Japan | Asia | as-east (Tokyo, Asia) |
| New Zealand | Default | na-east (Virginia, USA) |
| Saudi Arabia | Europe | eu-central (Frankfurt, Germany) |
| South Africa | Default | na-east (Virginia, USA) |
| Spain | Europe | eu-central (Frankfurt, Germany) |
| UAE | Asia | as-east (Tokyo, Asia) |
Option #2: Region Locking
With this option, you use a specific DeepAffex cluster URL for all network calls to the DeepAffex Cloud. In this scenario, the integrator can entirely bypass our routing rules and instead lock access to a specific DeepAffex cluster.
-
Data processing: Data will be processed by the specific DeepAffex cluster used.
-
Results storage: If your DeepAffex ORG is configured to store measurement results, then results will be stored by the specific DeepAffex cluster used.
If region locking is a requirement for you, then please use the direct regional URLs shown below. For these URLs, data is processed (and results stored if configured) on the DeepAffex cluster corresponding to the specified URL.
The as-hk (Hong Kong) cluster is available only through region locking.
No default-routing rule resolves to it, so it does not appear in the routing
rules or examples above — it can be reached exclusively via its direct regional
URL below.
Direct regional URLs
| Region | URL |
|---|---|
| North America (N. Virginia, USA) Short code: na-east | https://api.na-east.deepaffex.ai https://dashboard.na-east.deepaffex.ai https://awe.na-east.nuralogix.ai |
| Europe (Frankfurt, Germany) Short code: eu-central | https://api.eu-central.deepaffex.ai https://dashboard.eu-central.deepaffex.ai https://awe.eu-central.nuralogix.ai |
| South America (Sao Paulo, Brazil) Short code: sa-east | https://api.sa-east.deepaffex.ai https://dashboard.sa-east.deepaffex.ai https://awe.sa-east.nuralogix.ai |
| Asia (Tokyo, Japan) Short code: as-east | https://api.as-east.deepaffex.ai https://dashboard.as-east.deepaffex.ai https://awe.as-east.nuralogix.ai |
| Asia Pacific (Hong Kong, HK) Short code: as-hk | https://api.as-hk.deepaffex.ai https://dashboard.as-hk.deepaffex.ai https://awe.as-hk.nuralogix.ai |
Direct regional URLs (China)
| Region | URL |
|---|---|
| Mainland China (Beijing, China) Short code: cn-north | https://api.cn-north.deepaffex.cn https://dashboard.cn-north.deepaffex.cn https://awe.cn-north.nuralogix.cn |