[DevOps] Determine external dependents of CIE resources in `vaec-cms` that will be impacted by AWS account migration.

[ndouglas]

User Story

Followup to #86930.

As a DevOps engineer, I want to determine what things outside the vaec-cms AWS account would be impacted by an account migration to prevent downtime, errors, and other negative consequences for our team and other teams.

I need to dig up the architecture diagrams and trace through a few things, and also take into account our service accounts and other things that may be used for monitoring, etc.

Tasks

• [x] [DevOps] Determine things outside the vaec-cms account that would be impacted by an account migration and document them in this thread.

Acceptance Criteria

• [x] Things outside the vaec-cms account that would be impacted by an account migration have been documented in this thread.

[ndouglas]

Partial(?) list:

• Clinician Workflow
• VSE-CS we think
• VeTEXT
• vets-api
• vets-website

[ndouglas]

As documented elsewhere, it seems that Clinician Workflow will no longer depend on Vista API after October, and Clinical Staff will no longer depend on Vista API after September.

So the full list, as far as I know, is:

• VeTEXT
• vets-api
• vets-website