From 03ae2bfff64fa93d4aaabef436cf614accf32384 Mon Sep 17 00:00:00 2001 From: Anastasiia Tovpeko <114177030+atovpeko@users.noreply.github.com> Date: Fri, 7 Feb 2025 17:43:40 +0200 Subject: [PATCH] clarification about IPs (#3783) Co-authored-by: Iain Cox --- use-timescale/security/vpc.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/use-timescale/security/vpc.md b/use-timescale/security/vpc.md index f73ffd89d3..586a5905bb 100644 --- a/use-timescale/security/vpc.md +++ b/use-timescale/security/vpc.md @@ -97,6 +97,8 @@ between $CLOUD_LONG and your own VPC in a logically isolated virtual network. ![Create a new VPC in $CLOUD_LONG](https://assets.timescale.com/docs/images/tsc-vpc-create.png) + The IP ranges of the Peering VPC and Customer VPC should not overlap. + 1. For as many peering connections as you need: 1. In the `VPC Peering` column, click `Add`.