Routes determine how to direct traffic from your private space, for example,
to the public internet or through a connection (VPN or transit gateway).
You might want to add a route to enable a new subnet to be accessible or remove a route if you no longer want a subnet to be accessible through the transit gateway.
When you create a new private space, you can remove the default routes that MuleSoft provides. However, when you change the default route, your private space might experience downtime. If the X icon doesn’t appear for a route, you can’t remove it.
You cannot remove the MuleSoft-defined routes for existing private spaces created before March 9, 2023. You must create and configure a new private space to remove the default routes that MuleSoft defines. MuleSoft defines other routes, such as control plane traffic routes, that you cannot view or remove from the route table. Note that Anypoint MQ, ObjectStore v2, and API Manager require internet access from your network.
-
From Anypoint Platform, select Runtime Manager > Private Spaces.
-
Click the name of the private space to manage.
-
On the Network tab, in the Private Network section, click Route Table:
The route table shows all routes for the private space.
-
Add a route by entering the subnet in CIDR notation, selecting the connection,
and clicking Add Route:
You can’t add a route that matches a priority route (a route that’s used by your private network).
Routes can be used by only one connection at a time.
If you enter a non-local/Internet Gateway (IGW) route, CloudHub 2.0 warns that the route is being used by another connection.
Routes should not overlap with existing routes.
CloudHub 2.0 warns if you enter a route that overlaps with another route in the route table.
-
Remove a route by clicking the X icon for a row in the table and then clicking Delete to confirm.
If the X icon doesn’t appear for a route, you can’t remove it.
You can remove routes for static VPN connections.
-
Click Done to close the route table.
Anypoint Platform submits the new route to AWS.
|
|
You cannot add 169.254.168.0/22 (reserved by AWS) as a route destination.
|