IoT devices can be setup to use private and or shared SAPs in one or more regions simultaneously. Your upstream application server may also be integrated to one or more IoTGtw local/regional API/MQTT/SQS/Sockets Gateway cloud services to have partly meshed or fully meshed geo-resilient uplink and downlink data delivery.

To keep traffic local to a region/country for all or subset of your devices in a particular region (i.e. for the devices in Australia).

• Configure the devices in that region to use our service access gateway in Australia (If your devices support SimplyTiny then the device can be setup to dynamically retrieve the SAP list you have shortlisted/permitted on the device service template)
• Ensure your upstream application is hosted in the said region (in this example Australia).
• Login to the portal (or use provisioning APIs) to setup one or more customer endpoint profile that points to your upstream application servers in Australia
• Make the said endpiont profiles the preferred endpoint profiles for the devices by attaching the endpoint profiles to the device service template as the primary endpoints and secondary endpoints, etc.
• For the downstream communication from your upstream application to IoTGtw, ensure to select and use the IoTGtw API/MQTT/SQS/Sockets Gateway local to that region (Australia).

Note you can also configure a variation to the local routing by setting up the gateways of another region as the preferred backup to enable full geo-redundancy.