Skip to content

Commit 1f18ffe

Browse files
committed
fix(vpc): add routing date
1 parent 1688392 commit 1f18ffe

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

pages/vpc/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ Routing allows resources on Private Networks witin the same VPC to communicate w
133133
Each routed VPC has a [route table](#route-table) which is automatically populated with routes to each of its Private Networks. When you attach a Public Gateway to a Private Network, and tell it to advertise a default route to the internet, such routes are also added to the VPC's route table. You can also create your own [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route), to route traffic towards defined destination IP ranges towards specific "next hop" resources.
134134

135135
<Message type="note">
136-
If you have [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) routing behavior on your VPC, or created a VPC since TODODATE, routing takes on the following characteristics:
136+
If you have [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) routing behavior on your VPC, or created a VPC since July 1st 2025, routing takes on the following characteristics:
137137
- Custom routes are advertised across the entire VPC, instead of only on the Private Network of the resource designated as next hop.
138138
- You can optionally [enable each Private Network in the VPC to receive default route advertisements](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) not only from their locally attached Public Gateways, but from other Public Gateways (or default custom routes) attached to different Private Networks throughout the whole VPC.
139139
</Message>

pages/vpc/how-to/manage-routing.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ To activate routing on a pre-existing VPC, follow these steps:
4141

4242
## How to update routing behavior
4343

44-
If you created your VPC before TODODATE, you must manually update its routing behavior in order to get the following capabilities:
44+
If you created your VPC before July 1st 2025, you must manually update its routing behavior in order to get the following capabilities:
4545

4646
- Advertisement of custom routes across the entire VPC as standard.
4747
- Option to enable each Private Network in the VPC to receive default route advertisements not only from their locally attached Public Gateways, but from other Public Gateways (or default custom routes) attached to different Private Networks throughout the whole VPC.
@@ -163,7 +163,7 @@ For example, you may wish to route all traffic for a certain private IP range to
163163

164164
<Message type="note">
165165
The scope of custom routes depends on whether your VPC is using up-to-date routing behavior:
166-
- If you created your VPC after TODODATE, or have [manually updated its routing behavior](#how-to-update-routing-behavior), custom routes are advertised across the entire VPC.
166+
- If you created your VPC after July 1st 2025, or have [manually updated its routing behavior](#how-to-update-routing-behavior), custom routes are advertised across the entire VPC.
167167
- Otherwise, custom routes are scoped only to the Private Network(s) of the "next hop" resource and not advertised to other Private Networks in the VPC. In this case, for the scenario mentioned above of routing traffic towards a VPN tunnel, the origin of the packet must be in the same Private Network as the resource hosting the VPN.
168168
</Message>
169169

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,9 +75,9 @@ For example, you may use one Private Network for frontend resources and another
7575

7676
## Updating routing behavior
7777

78-
From TODO DATE, new routing behavior is available for VPCs.
78+
From July 1st 2025, new routing behavior is available for VPCs.
7979

80-
- This routing behavior will be applied automatically to VPCs created after TODO DATE, or to pre-existing VPCs that only activate routing after this date.
80+
- This routing behavior will be applied automatically to VPCs created after July 1st 2025, or to pre-existing VPCs that only activate routing after this date.
8181
- Pre-existing VPCs already using routing must be [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) to accept this new behavior
8282

8383
| | Old behavior | New behavior |

0 commit comments

Comments
 (0)