Skip to content

Commit 093c979

Browse files
RoRoJjcirinosclwy
andcommitted
Update pages/vpc/reference-content/understanding-routing.mdx
Co-authored-by: Jessica <[email protected]>
1 parent aa6c08b commit 093c979

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

pages/vpc/reference-content/understanding-routing.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ From TODO DATE, new routing behavior is available for VPCs.
8787

8888
### Custom routes
8989

90-
Previously, custom routes were scoped only to the Private Network(s) of the “next hop” resource. Their routes were not propagated to other Private Networks in the VPC. For example, in the scenario of using a custom route to route traffic towards a VPN tunnel, the origin of the packet had be in the same Private Network as the resource hosting the VPN.
90+
Previously, custom routes were scoped only to the Private Network(s) of the “next hop” resource. Their routes were not propagated to other Private Networks in the VPC. For example, in the scenario of using a custom route to route traffic towards a VPN tunnel, the origin of the packet had to be in the same Private Network as the resource hosting the VPN.
9191

9292
With new routing behavior, custom routes are scoped to the entire VPC as standard. All Private Networks in the VPC receive route advertisements for all custom routes. This gives enhanced flexibility when using custom routes to route traffic towards VPN tunnels.
9393

0 commit comments

Comments
 (0)