From 2a8832fa39fe06e9dd66f2d40b49765af0b2b16b Mon Sep 17 00:00:00 2001 From: Pablo Alberto Camino Date: Thu, 20 Mar 2025 10:29:33 -0300 Subject: [PATCH] Update vpc-provisioning-concept.adoc --- cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc b/cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc index 69aa4ab6d..e5e49971b 100644 --- a/cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc +++ b/cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc @@ -92,6 +92,13 @@ When the deployment region matches the VPC region: When the deployment region does not match the VPC region, the app is deployed outside of the VPC. This means that the app does not have access to any connectivity methods configured for the VPC. +== FAQ: Can an environment be associated with more than a single VPC? + +Yes, an environment may be assigned to more than one VPC provided that those VPC reside in different regions. +When an application is deployed to that environment the VPC it is deployed to is defined based on the deployment region. +If the environment is not specifically associated to a VPC in that region then the default VPC for that region will be used. +If environment is associated to a new VPC within the same region of a previously assigned VPC this association will replace previous one, but applications already deployed will keep running on the previous VPC until restarted. + == See Also * xref:to-request-vpc-connectivity.adoc[Request VPC Connectivity to Your Network]