Routing Targets

What is a Routing Target?

A Routing Target defines where your endpoint traffic is delivered: an internet breakout, a private VPN tunnel, or a direct cloud connection.

Routing Targets belong to a VSlice. Every Routing Target, Routing Policy, and Endpoint Group used together must belong to the same VSlice.

Routing Target Types

Internet

Provides a public internet breakout. Stacuity allocates a public IP address and applies NAT. Configuration required: None.

VPN (IPSec)

An encrypted private tunnel. Endpoint traffic is forwarded with no NAT — the device's private IP is passed end-to-end.

Configuration required: Gateway IP, pre-shared key or certificate, IKE/ESP settings, protected subnets.

WireGuard

A modern, lightweight VPN protocol. Configuration required: server public key, endpoint address and port, allowed IPs.

Cloud and Direct Connect Types

AWS Direct Connect, Azure ExpressRoute, Google Interconnect, Cross Connect, and Direct Peering appear in the portal but are not self-service. Contact your tenant administrator to request these.

Settings Fixed at Creation

Setting	Notes
VSlice	Cannot be changed.
Region	Asia / Brazil (Beta) / Europe / North America / Australia (Beta). Cannot be changed.
Redundancy Zone	Cannot be changed.
Target Type	Cannot be changed.

Settings That Can Be Changed

Setting	Notes
Name	Human-readable label.
Moniker	5–30 characters. API identifier.

Create a Routing Target

Steps:

Go to Configuration → Routing Targets.
Click Add.

Fill in the fields and click Create.

Field	Required	Changeable?	Notes
VSlice	Yes	No
Name	Yes	Yes	5–100 characters.
Moniker	Yes	Yes	5–30 characters.
Region	Yes	No
Redundancy Zone	Yes	No
Target Type	Yes	No

Edit a Routing Target

Editable fields: Name, Moniker only.

VSlice, Region, Redundancy Zone, and Target Type cannot be changed after creation.

Delete a Routing Target

A Routing Target cannot be deleted while it is referenced by a Routing Policy rule. Remove or update those rules first.