Skip to main content

Connecting to the RTGS.global API

The RTGS.global Gateway uses a hub-and-spoke network architecture. Your systems must connect to the RTGS.global Gateway virtual network (vNet) to access the API.

Connection Options​

MethodDescription
VPN / ExpressRoute GatewayConnect using Azure VPN Gateway or Azure ExpressRoute
Virtual Network PeeringPeer an existing vNet directly to the RTGS.global Gateway vNet
Jumpbox or BastionConnect via a virtual machine acting as a gateway

Jumpbox Deployment (for Validation)​

A sample deployment template is provided to simplify initial validation. It provisions:

  • A Windows 11 virtual machine
  • A virtual network
  • A public IP

Configuration​

Step 1 — Subscription and resource group

Select the target subscription and resource group. These do not need to match the RTGS.global Gateway deployment.

Step 2 — Jumpbox credentials

Set the username and password for the virtual machine.

Required Configuration Values​

Two values are needed from your existing RTGS.global Gateway deployment:

  • The vNet from the RTGS.global Gateway managed app — typically named rtgs-aca-internal-vnet
  • The private DNS Zone for the container app with suffix *.azurecontainerapps.io

An ARM template is available for download and customisation if the sample deployment does not meet your requirements.