Tech spec for re-implementing infra using the v0.2.0 release of the infra template

[rocketnova]

Context

The MWDP project originated the infra template. Since then, a lot of progress has happened on the infra template, but this project's infra has stayed static.

In this previous tech spec, we outlined what it would look like to migrate to the infra template. This tech spec asks a slightly different question. I would like to know what it would take to re-implement the infra for the eligibility screener (in other words, starting over) using v0.2.0 release of the infra template. Imagine we could destroy the current AWS account and start fresh.

Tasks

Create a tech spec that:

1. Outlines what AWS resources are needed to deploy the eligibility screener (e.g. ECR, ECS, IAM, etc)
2. Outlines the new CI/CD process and any changes that need to be made to the github repo
3. Explains pros/cons of re-implementing
4. Outlines risks for re-implementing
5. Estimates the amount of effort to re-implement
6. Outlines the plan for re-implementing
7. Outlines the plan for testing the implementation (can be very simple!)

Notes: This tech spec can and should re-use content from the previous tech spec where relevant.

[rocketnova]

@aplybeah Is it easy to compare against the v0.3.0 release of the template-infra instead of the v0.2.0 version?

[aplybeah]

@rocketnova Because the screener is so behind, I'd say its about the same. I'd rather compare against the v0.3.0 version, since that's more up to date.

[rocketnova]

@aplybeah Sounds good. Thank you!