From ae048cd60923ab93d0d806898a9c1da16427f16d Mon Sep 17 00:00:00 2001 From: Iain Date: Wed, 13 Nov 2024 17:37:14 +0100 Subject: [PATCH 1/7] feat: add information on multiple VPCs. --- use-timescale/vpc.md | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index 83f1396461..f043519994 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -11,12 +11,12 @@ cloud_ui: # Secure your $CLOUD_LONG services with VPC Peering and AWS PrivateLink -You use Virtual Private Cloud ($VPC) peering to ensure that your $CLOUD_LONG services are +You use Virtual Private Cloud ($VPC) peering to ensure that your $SERVICE_LONG are only accessible through your secured AWS infrastructure. This reduces the potential attack vector surface and improves security. The data isolation architecture that ensures a highly secure connection between your apps and -$CLOUD_LONG: +$CLOUD_LONG is: VPC][console-vpc], click `New VPC`. The number of VPCs you can attach to your project depends on your [pricing plan][pricing-plans]. If you - need more VPCs either contact contact [support@timescale.com](mailto:support@timescale.com) or change + need more VPCs either contact [support@timescale.com](mailto:support@timescale.com) or change your pricing plan in $CONSOLE. Each $CLOUD_LONG VPC can have as many peering connections as you need. 1. Choose your region and IP range, then click `Create VPC`. @@ -227,3 +236,4 @@ some time for DNS propagation. [create-service]: /getting-started/:currentVersion:/services/#create-a-timescale-cloud-service [pricing-plans]: /about/:currentVersion:/pricing-and-account-management/ +[project-members]: /use-timescale/:currentVersion:/members/ From 610ee87ee4b6bf9ab35fa83f4a61f9eebfeb2a52 Mon Sep 17 00:00:00 2001 From: Iain Date: Thu, 14 Nov 2024 10:27:27 +0100 Subject: [PATCH 2/7] feat: add information on multiple VPCs. --- use-timescale/vpc.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index f043519994..f75adb8bc7 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -35,18 +35,19 @@ peering connection to your Customer VPC, you use AWS Security Groups to restrict the services in your Customer VPC that are visible to the Peering VPC. The last step is to attach individual services to the Peering VPC. -* You define each $CLOUD_LONG $VPC in your [$CLOUD_LONG project][project-members]. -* You can attach any number of Customer VPCs to a $CLOUD_LONG $VPC. +* You define each $CLOUD_LONG $VPC on a [$CLOUD_LONG project level][project-members]. * You can attach: - * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time. - The $SERVICE_SHORT and $VPC must be in the same AWS region. - * Multiple $SERVICE_LONG to the same $CLOUD_LONG $VPC. -* You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPC at the same time. -* To support multiple AWS regions, you need multiple $CLOUD_LONG $VPC. - -The number of $CLOUD_LONG $VPC s you have in your project depends on your [pricing plan][pricing-plans]. + * Any number of Customer $VPCs to a $CLOUD_LONG $VPC. + * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time. + + The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple + $CLOUD_LONG $VPCs. + * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. +* You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time. + +The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans]. If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your -pricing plan in $CONSOLE. +pricing plan in [$CONSOLE][console-login]. ## Prerequisites From 652323e20a571360f701489c6b6b0bcc49c9efba Mon Sep 17 00:00:00 2001 From: Iain Date: Thu, 14 Nov 2024 10:38:01 +0100 Subject: [PATCH 3/7] feat: add information on multiple VPCs. --- use-timescale/vpc.md | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index f75adb8bc7..f2cb5bf947 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -18,9 +18,7 @@ attack vector surface and improves security. The data isolation architecture that ensures a highly secure connection between your apps and $CLOUD_LONG is: - +![$CLOUD_LONG isolation architecture](https://assets.timescale.com/docs/images/tsc-vpc-architecture.svg) Your apps run inside your AWS Customer VPC, your services always run inside the secure $CLOUD_LONG $VPC. You control secure communication between apps in @@ -79,9 +77,21 @@ between $CLOUD_LONG and your own VPC in a logically isolated virtual network. 1. In [$CONSOLE > VPC][console-vpc], click `New VPC`. - The number of VPCs you can attach to your project depends on your [pricing plan][pricing-plans]. If you - need more VPCs either contact [support@timescale.com](mailto:support@timescale.com) or change - your pricing plan in $CONSOLE. Each $CLOUD_LONG VPC can have as many peering connections as you need. + ![$CLOUD_LONG new $VPC](https://assets.timescale.com/docs/images/console-add-vpc.png) + + * You can attach: + * Any number of Customer $VPCs to a $CLOUD_LONG $VPC. + * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time. + + The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple + $CLOUD_LONG $VPCs. + * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. + * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time. + + The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans]. + If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your + pricing plan in [$CONSOLE][console-login]. + 1. Choose your region and IP range, then click `Create VPC`. From 62aa72002607ba4549578b3311744032f4c98382 Mon Sep 17 00:00:00 2001 From: Iain Cox Date: Thu, 14 Nov 2024 10:55:05 +0100 Subject: [PATCH 4/7] Apply suggestions from code review Co-authored-by: atovpeko <114177030+atovpeko@users.noreply.github.com> Signed-off-by: Iain Cox --- use-timescale/vpc.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index f2cb5bf947..5b1508af6d 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -11,7 +11,7 @@ cloud_ui: # Secure your $CLOUD_LONG services with VPC Peering and AWS PrivateLink -You use Virtual Private Cloud ($VPC) peering to ensure that your $SERVICE_LONG are +You use Virtual Private Cloud ($VPC) peering to ensure that your $SERVICE_LONGs are only accessible through your secured AWS infrastructure. This reduces the potential attack vector surface and improves security. @@ -43,7 +43,7 @@ The last step is to attach individual services to the Peering VPC. * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time. -The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans]. +The number of $CLOUD_LONG $VPCs you can create in your project depends on your [pricing plan][pricing-plans]. If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your pricing plan in [$CONSOLE][console-login]. @@ -88,7 +88,7 @@ between $CLOUD_LONG and your own VPC in a logically isolated virtual network. * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time. - The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans]. + The number of $CLOUD_LONG $VPCs you can create in your project depends on your [pricing plan][pricing-plans]. If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your pricing plan in [$CONSOLE][console-login]. From 835d7069034fdf2f36dc4c7768c8c896035640db Mon Sep 17 00:00:00 2001 From: Iain Date: Thu, 14 Nov 2024 11:16:10 +0100 Subject: [PATCH 5/7] chore: updates on review. --- use-timescale/vpc.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index 5b1508af6d..26dea59960 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -20,18 +20,18 @@ $CLOUD_LONG is: ![$CLOUD_LONG isolation architecture](https://assets.timescale.com/docs/images/tsc-vpc-architecture.svg) -Your apps run inside your AWS Customer VPC, your services always run +Your Customer apps run inside your AWS Customer VPC, your $CLOUD_LONG services always run inside the secure $CLOUD_LONG $VPC. You control secure communication between apps in -your VPC and your services using a dedicated Peering VPC. The AWS PrivateLink connecting -$CLOUD_LONG $VPC to the dedicated Peering VPC gives the same level of protection as using a direct -AWS PrivateLink connection. It only enables communication to be initiated from your Customer VPC -to services running in the $CLOUD_LONG $VPC. $CLOUD_LONG cannot initiate communication with your VPC. +your VPC and your $SERVICE_SHORTs using a dedicated Peering $VPC. The AWS PrivateLink connecting +$CLOUD_LONG $VPC to the dedicated Peering $VPC gives the same level of protection as using a direct +AWS PrivateLink connection. It only enables communication to be initiated from your Customer $VPC +to services running in the $CLOUD_LONG $VPC. $CLOUD_LONG cannot initiate communication with your $VPC. -To configure this secure connection, you first create the Peering VPC with +To configure this secure connection, you first create the $CLOUD_LONG Peering $VPC with AWS PrivateLink in $CONSOLE. After you have accepted and configured the -peering connection to your Customer VPC, you use AWS Security Groups to -restrict the services in your Customer VPC that are visible to the Peering VPC. -The last step is to attach individual services to the Peering VPC. +peering connection to your Customer $VPC, you use AWS Security Groups to +restrict the services in your Customer $VPC that are visible to the Peering $VPC. +The last step is to attach individual services to the Peering $VPC. * You define each $CLOUD_LONG $VPC on a [$CLOUD_LONG project level][project-members]. * You can attach: From a1e0cd4821704576846de583386270dd0d9a71bc Mon Sep 17 00:00:00 2001 From: Iain Date: Thu, 14 Nov 2024 11:28:06 +0100 Subject: [PATCH 6/7] chore: updates on review. --- use-timescale/vpc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index 26dea59960..281657278d 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -20,7 +20,7 @@ $CLOUD_LONG is: ![$CLOUD_LONG isolation architecture](https://assets.timescale.com/docs/images/tsc-vpc-architecture.svg) -Your Customer apps run inside your AWS Customer VPC, your $CLOUD_LONG services always run +Your customer apps run inside your AWS Customer VPC, your $CLOUD_LONG services always run inside the secure $CLOUD_LONG $VPC. You control secure communication between apps in your VPC and your $SERVICE_SHORTs using a dedicated Peering $VPC. The AWS PrivateLink connecting $CLOUD_LONG $VPC to the dedicated Peering $VPC gives the same level of protection as using a direct From e23f93d4302350eeca1764be0c4e0423b30bd628 Mon Sep 17 00:00:00 2001 From: Iain Date: Thu, 14 Nov 2024 19:11:05 +0100 Subject: [PATCH 7/7] chore: updates on review. --- use-timescale/vpc.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/use-timescale/vpc.md b/use-timescale/vpc.md index 281657278d..95be2d6b67 100644 --- a/use-timescale/vpc.md +++ b/use-timescale/vpc.md @@ -35,11 +35,11 @@ The last step is to attach individual services to the Peering $VPC. * You define each $CLOUD_LONG $VPC on a [$CLOUD_LONG project level][project-members]. * You can attach: - * Any number of Customer $VPCs to a $CLOUD_LONG $VPC. + * Up to 50 Customer $VPCs to a $CLOUD_LONG $VPC. * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time. - The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple - $CLOUD_LONG $VPCs. + The $SERVICE_SHORT and $VPC must be in the same AWS region. However, you can peer a Customer $VPC and a + $CLOUD_LONG $VPC that are in different regions. * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time. @@ -80,11 +80,11 @@ between $CLOUD_LONG and your own VPC in a logically isolated virtual network. ![$CLOUD_LONG new $VPC](https://assets.timescale.com/docs/images/console-add-vpc.png) * You can attach: - * Any number of Customer $VPCs to a $CLOUD_LONG $VPC. + * Up to 50 Customer $VPCs to a $CLOUD_LONG $VPC. * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time. - The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple - $CLOUD_LONG $VPCs. + The $SERVICE_SHORT and $VPC must be in the same AWS region. However, you can peer a Customer $VPC and a + $CLOUD_LONG $VPC that are in different regions. * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC. * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time.