From abc460983f48a48f8bdb1687f19734ac78201682 Mon Sep 17 00:00:00 2001 From: Heathpackard Date: Tue, 3 Jun 2025 15:48:47 +1200 Subject: [PATCH] Update vpc-peering-set-up-guide.mdx --- .../(deployment)/set-up-guides/vpc-peering-set-up-guide.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/guides/(deployment)/set-up-guides/vpc-peering-set-up-guide.mdx b/content/docs/guides/(deployment)/set-up-guides/vpc-peering-set-up-guide.mdx index f8c18f9..4d847c5 100644 --- a/content/docs/guides/(deployment)/set-up-guides/vpc-peering-set-up-guide.mdx +++ b/content/docs/guides/(deployment)/set-up-guides/vpc-peering-set-up-guide.mdx @@ -11,11 +11,11 @@ updatedAt: "Tue Jul 30 2024 19:05:55 GMT+0000 (Coordinated Universal Time)" Peering VPCs is currently a manual process involving several steps: -1. Collect the required information to set up peering connections +1. Collect the required information to set up peering connections. 1. Which AWS accounts and VPCs do you want to peer? 2. What are the CIDR block(s) dedicated to those VPCs? 2. Contact your UserClouds team to get our AWS account and VPC ID information. 3. Create a peering request by following the AWS instructions here. -4. UserClouds’ infrastructure team will accept the request -5. Configure the appropriate route tables to ensure data is routed correctly across the peering connection +4. UserClouds’ infrastructure team will accept the request. +5. Configure the appropriate route tables to ensure data is routed correctly across the peering connection. 6. \_(optional) \_Configure internal DNS to point across the VPC peering connection. If you aren’t already running internal DNS, UserClouds can repoint our public DNS to make this work.