cds-snc / notification-planning-core

Project planning for GC Notify Core Team
0 stars 0 forks source link

Investigate and create a plan to run GC Notify on a secondary Cloud Service Provider #72

Open ben851 opened 1 year ago

ben851 commented 1 year ago

Description

As an operator of GC Notify, I would like to be able to roll over/fall back on a secondary cloud service provider in the event that AWS has major issues in regions.

WHY are we building?

As evidenced by the ice storm in April 2023, GC Notify can be impacted if an AWS availability zone goes down. In order to increase resiliency of GC Notify, we should be able to deploy the entire infrastructure to a secondary CSP.

WHAT are we building?

This will require a full review of our existing infrastructure to identify where we are using AWS specific resources. Once these are identified, we should investigate moving these resources to cloud agnostic alternatives (i.e. move lambda functions to Kubernetes).

Once this is done, we will need to identify a secondary CSP (most likely Azure) and begin transcoding our AWS terraform code to Azure terraform.

VALUE created by our solution

GC Notify will be much more resilient to major CSP outages.

Acceptance Criteria

QA Steps