Test the application’s failover, monitoring, alerting, outage, and recovery processes.

[ustaxcourt]

Test the application’s failover, monitoring, alerting, outage, and recovery processes.

[vickimcfadden]

intention is to do chaos, fuzz, and load testing together in a sprint.

[vickimcfadden]

@adunkman to follow up with Kelsey & groom issue.

[vickimcfadden]

Can get the work ready in development environment and may be able run in migration environment.

[adunkman]

Going to drop myself as an assignee to reflect reality since Julia is running with this; always happy to assist if needed!

[julialeague]

Logged #586 to address the lack of automatic lambda failover configuration.

[julialeague]

Here are the notes I've taken throughout working on this issue:
https://docs.google.com/document/d/15zCf3F2RRoFbOO-0t8j5AXJCR1ad-Nz2uSw7j892OdM/edit?usp=sharing (only visible to GSA users and folks I've explicitly shared to)

[julialeague]

To do: Log the rest of the bold line items from my testing doc that aren't needing risk acceptance discussion with @mmarcotte. Log a follow-up issue to discuss risk acceptance-related questions and document the conclusions.

[julialeague]

Per the discussion with Mike Marcotte on Wednesday, I'll log an issue to revisit resiliency testing in the future, since we don't have any automated processes doing this sort of testing for us.

[julialeague]

Logged #747 to revisit this testing at a later date.

[julialeague]

The epic for failover-related issues: #631