Ensure that U-DS Shared Services are Deployed to Unity-Test AWS Account and Accessible by SPS

[galenatjpl]

As a prerequisite of https://github.com/unity-sds/unity-project-management/issues/71, U-DS services need to be deployed to the Unity-Test AWS account. As far as I know, this includes at least:

• DAPA API (entries in the shared services API GW)
• Data Catalog

These will be utilized (pointed to) by the SPS deployment in the Unity-Sips-Test account.

@ngachung , please comment on this ticket if you think there are additional U-DS shared services that I missed in the above list, that are necessary for the SIPS deployment.

Acceptance Critieria:

• [ ] https://github.com/unity-sds/unity-cs/issues/194 is completed
• [ ] https://github.com/unity-sds/unity-cs/issues/195 is completed
• [ ] https://github.com/unity-sds/unity-cs/issues/196 is completed
• [ ] https://github.com/unity-sds/unity-cs/issues/197 is completed
• [ ] https://github.com/unity-sds/unity-cs/issues/198 is completed
• [ ] DAPA API GW routes are deployed to Unity-Test, and is proven to be accessible by SPS in the Unity-SPS-Test account
• [ ] Data Catalog is deployed to Unity-Test, and is proven to be accessible by SPS in the Unity-SPS-Test account

[ngachung]

That's accurate. UDS shared services are currently deployed to Unity-Test. What we need to test is the accessibility.

[galenatjpl]

Adding @jjacob7734 to this ticket as well, since he says the U-AS will be responsible for the DAPA-"P" portion of the DAPA API, and this deployment should be on Joe's radar.