Document architecture to define current CyHy VS system

[chelsgr]

Summary

Multiple business objectives have initiated interested in updated architecture documentation for the CyHy VS system as it is today including: 1. ATO renewal in progress with the existing authorization expiring at the end of September, 2. VM Leadership has established a goal to document our systems and workflows, and 3. The data lead is requesting this information.

Motivation and context

To elaborate, here are more details on each business justification for completing the architectural diagrams of the existing system:

1. Initially the goal was to provide the newly designed CyHy architecture for the ATO renewal. However, given the shifting strategy goals and team responsibilities in the realignment - we expect there will likely be delays to the CyHy Scalability initiative's previously established timeline. The timeline used to overlap with the renewal, but delays would mean the system needs to be reaccredited with the current architectural diagrams. More details on the ATO renewal are on: https://github.com/cisagov/cool-system-internal/issues/129
2. The goal referenced includes the scope:

7. Document and Validate VM systems and data architecture (Q3)
   a. Current workflow, internal/external dependencies, and limitations

3. @chelsgr has been working with the lead of the data team and requestors to press the need to entirely move corresponding scope to the responsible enterprise teams (especially any long-term data storage projects/tasks). In response, she has requested current CyHy architectural diagrams to assist her understanding of the system boundaries to facilitate support.

Acceptance criteria

• Documented architecture diagrams for the current CyHy system architecture.
• Nice to have: diagrams for the intended rewrite changes and rough estimates of when we intend to make the changes.