Why is the route53-private zone regional in the Reference Architecture?
Looking over the [service catalog for-production example](https://github.com/gruntwork-io/terraform-aws-service-catalog), i see that the route-53 private zone is defined underneath [each accounts regional area](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/infrastructure-live/dev/us-west-2/dev/networking/route53-private). However, Route53 is a global service, so it seems odd to treat it as regional. Why is it regional and not global?
Private Route 53 Zones are associated with VPCs, which are regional. In the Ref Arch/service catalog example we are only associating with a single VPC in a single region, so it makes sense to treat it as regional. On the other hand, it would make more sense to be in the global folder if the zone is going to be associated with multiple VPCs in different regions. With that said, the way to organize the infrastructure in the folders is entirely up to the end user. So if it is easier to think about the resources by the service, then there is nothing wrong with putting the Route 53 private zone in the global folder. You can always [migrate folders](https://github.com/gruntwork-io/knowledge-base/discussions/229) to refactor the Reference Architecture in whatever way suits your need.