Right now framework stack components exist in a single region, meaning that app authentication relies on that region being online. Ideally all of our GitHub app components would support multiple regions, at least for availability, but also for performance. The other components of our GitHub app are deployed this way: we have us-west-2 as our primary region, but our transactions are replicated to eu-west-1. We have CloudFront with Lambda@Edge handling webhook verification and ingestion from GitHub, Route53 latency based routing for our function URLs, and Lambdas deployed to both regions that can handle events from anywhere. That way we're not dependent on a single region being online.
This stack is using DynamoDB and Lambda, with a little bit of KMS signing. DDB supports global tables, which would be ideal for this, and KMS keys can be multi-region. Could this stack be updated to support a multi-region deployment?
Right now framework stack components exist in a single region, meaning that app authentication relies on that region being online. Ideally all of our GitHub app components would support multiple regions, at least for availability, but also for performance. The other components of our GitHub app are deployed this way: we have us-west-2 as our primary region, but our transactions are replicated to eu-west-1. We have CloudFront with Lambda@Edge handling webhook verification and ingestion from GitHub, Route53 latency based routing for our function URLs, and Lambdas deployed to both regions that can handle events from anywhere. That way we're not dependent on a single region being online.
This stack is using DynamoDB and Lambda, with a little bit of KMS signing. DDB supports global tables, which would be ideal for this, and KMS keys can be multi-region. Could this stack be updated to support a multi-region deployment?