The legacy way of multi-regional and multi-account infrastructure management
Until now, our stack deployment was primarily focused on provisioning resources within a single AWS account and region. But what if we needed to provision the same stack in several regions? Let’s say we need to provision the same stack in Ireland, North Virginia, and Frankfurt.
Usually, the default region (for example, the API endpoint that we want to connect to) is chosen either from environment variables or from a local config file. When you invoke any command via awscli, it will connect to that specific default region.
We can also specify the region manually as an argument. So, if we want to provision the same stack in different regions, we have to repeat the same command that changes the argument value, as illustrated here:
aws cloudformation deploy --region eu-west-1 --template-file foo.yamlaws cloudformation deploy --region us-east-1 --template-file foo.yaml aws cloudformation deploy...
