Adding a new account to RA - how to deploy the VPC when CIDR is required?

[drafie]

I am following the guide 06-adding-a-new-account.md and it is not in sync with the latest RA. You can find the same documentation online here: https://docs.gruntwork.io/guides/reference-architecture/example-usage-guide/adding-a-new-account/deploy-the-ecs-deploy-runner

The problem is that somewhere in this guide, a step seems to be missing relating to VPCs that are needed for mgmt and apps.

If you follow the outdated guide - and attempt to deploy the ECS Deploy Runner - you will discover (among other things) that when you run terragrunt apply, you receive errors complaining about missing cidr_block variables. If you trace those errors back - you find /common.hcl requires the new account's CIDRs for VPCs for MGMT and likely APP (mgmt_vpc_cidrs app_vpc_cidrs variables).

The MGMT VPC is the very thing you are attempting to create so of course we don't have the CIDR values yet.

Since the documentation is out of date, or at least not in sync with the RA that was deployed for us, I don't know if I missed a step somewhere earlier. Are we supposed to use the gruntwork CLI to create these accounts if we are RA customers?

---

Tracked in ticket #109748

[drafie]

The answer -

These need to be manually set in the /common.hcl file at the root of the RA prior to running terragrunt run-all apply.

So it is something like this:

 mgmt_vpc_cidrs = {
    dev      = "172.31.80.0/20"
    logs     = "172.31.80.0/20"
    prod     = "172.31.80.0/20"
    security = "172.31.80.0/20"
    shared   = "172.31.80.0/20"
    stage    = "172.31.80.0/20"
    **NEWACCOUNT = "172.31.80.0/20"**
  }

 
  app_vpc_cidrs = {
    dev   = "10.0.0.0/16"
    prod  = "10.4.0.0/16"
    stage = "10.2.0.0/16"
    **NEWACCOUNT = "10.0.0.0/16"**
  }