VPC CIDRS for cross-region peering #13
-
This message was extracted from a discussion that originally took place in Gruntwork Community Slack. Names and URLs have been removed where appropriate From a customer Picking through our new reference architecture deployment, I have a strategic question about VPC CIDRs related to cross-region peering: the I guess we could change:
to
and update all the Terragrunt code accordingly, but would that send us down a bad path of messing too deeply with the base of the reference architecture? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
From a grunt Hey, Adam! So I’ve actually asked for some help from our subject matter experts on the Ref Arch & here’s the answer:
(see https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/examples/for-production/infrastructure-live/dev/us-west-2/dev/networking/vpc/terragrunt.hcl#L49)
make sure that you’re not missing any references as well (e.g. |
Beta Was this translation helpful? Give feedback.
From a grunt
Hey, Adam! So I’ve actually asked for some help from our subject matter experts on the Ref Arch & here’s the answer:
app_vpc_cidrs
to include the region, and then update the references to inject the region accordingly.common.hcl
in whatever shape works for you!Here’s the example steps:
app_vpc_cidrs
to look like the following: