Skip to content

W-18069215 – Add FAQ on assigning an environment to multiple VPCs #776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: latest
Choose a base branch
from
Open

W-18069215 – Add FAQ on assigning an environment to multiple VPCs #776

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions cloudhub/modules/ROOT/pages/vpc-provisioning-concept.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]