Reference Architecture - Can we use a different primary region per environment?
A customer asked: > We'd like our logs, security and shared accounts to use `us-east-1` as their primary region. However, dev, stage and prod should be deployed in `sa-east-1`. How can we define the different regions for use in different accounts?
Unfortunately, we don’t currently support a mixed region Reference Architecture deployment. We’re able to provide the Ref Arch at a flat fee with a quick turnaround due to our standardization, which means the limited options in the form are the only things we can support in deployment. Given your use case, I recommend deploying the Ref Arch in the us-east-1 region, and then migrating the app setup to sa-east-1 post deploy. The steps to do this are: - Copy paste the us-east-1 folder into a new sa-east-1 folder in each of the environments dev, stage, and prod. - Update the region.hcl file to point to sa-east-1 - Copy all secrets manager entries in us-east-1 into sa-east-1 - Update ARN references to secrets manager entries in the code to point to the newly copied secrets manager entries in sa-east-1. - Run terragrunt run-all apply in the sa-east-1 folder. Note that Gruntwork is happy to help out in support if you run into any issues going through this process.