From bcda825a6b551c93bb33551c1cf09ae3944b3e10 Mon Sep 17 00:00:00 2001 From: Logan McDonald Date: Fri, 19 Aug 2022 10:33:20 -0400 Subject: [PATCH] Cloud.gov ADR (#61) * add cloud.gov adr * talk about alternatives considered --- docs/architecture/decisions/0006-cloud-gov.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/architecture/decisions/0006-cloud-gov.md diff --git a/docs/architecture/decisions/0006-cloud-gov.md b/docs/architecture/decisions/0006-cloud-gov.md new file mode 100644 index 000000000..618166fe4 --- /dev/null +++ b/docs/architecture/decisions/0006-cloud-gov.md @@ -0,0 +1,25 @@ +# 6. Cloud.gov + +Date: 2022-08-12 + +## Status + +Accepted + +## Context + +We need a place to run our application for the registrar. Cloud.gov is a FIMSA Moderate Fedramped solution that supports our language and framework selections. + +## Decision + +To use cloud.gov to host our application(s). + +## Consequences + +Choosing cloud.gov for our solution means we are locked into its opinionated choices for our infrastructure. It forces us to run 12-factor applications. It doesn't support brokering for services we may need like email notifications. + +It also means the compliance lift is much lighter. We do not need to prove we are compliance for the majority of our infrastructure and our runtime enviornment. + +## Alternatives Considered + +Run our application on in either CISA's Azure or AWS environment with a continerized deployment.