Deployment of the same environment in multiple regions

[wasker]

I'm looking to deploy a prod environment in multiple regions. My plan is to share KV, Log Analytics, and CosmosDB instances between regional ACA deployments. I'd like to avoid managing non-compute resources separately/manually. Is there some recipe I could follow to achieve this?

[wasker]

It looks like in Aspire/AZD environment and location have strong connection, which complicate what I want to achieve. The environment is deployed into a single resource group in a single location; it's impossible to deploy same environment into a different location once one location is present.

After experimenting with a few ideas, the approach I arrived at is:

1. Have a separate AZD "shared" project, where shared resources (KV, DB, etc.) go. This is pure Bicep IaC, deployed first and in general has its own lifecycle, disconnected from the Aspire-based project.
2. Add a new serviceEnvironment parameter to the Aspire-based project.
3. Create and deploy "prod-<region1>" and "prod-<region2>" environments with AZD with parameters:
   • location = <region1> or <region2>.
   • serviceEnvironment = "prod" - this one can be used for constructing Bicep conditional expressions during provisioning. E.g., use insecure ingress in CAE which sits behind AFD (SSL termination) only in production.
4. Configure KV, DB, etc. as "existing" in Aspire; their names/locations come from parameters.

In other words, I deploy "prod" environment of the shared project first (KV and DB), then I deploy "prod-eastus" and "prod-westus" environments of the Aspire-based project where I use coordinates of the shared KV and DB as parameters and set serviceEnvironment to "prod" in both cases.