Create Backend API to Serve Health Statuses of Deployed services in a proj/venue

[galenatjpl]

This is an API that the UI can query to get the health statuses.

Backed API is responsible for reading JSON health status file stored in S3 bucket, and parses file, and returns a JSON response that indicates the health statuses of the services. The first consumer of this information will be a UI/UX web page displaying the statuses.

This API will:

1. Be implemented in the existing Go backend code/API area of the management console (https://github.com/unity-sds/unity-management-console)
2. Will be fronted by an API Gateway entry point that looks like: https://unity.com/project/venue/health

Acceptance Criteria:

• Ticket for implementing lambda is complete : Implement lambda in Venue account to periodically gather health status #367
• Ticket for S3 bucket creation is complete : Create Monitoring S3 bucket upon Management Console deployment #380
• Ticket for S3 SSM parameter creation is complete : Create SSM parameter for monitoring S3 bucket name #370
• API Gateway setup gets created by the run.sh (deployment of a venue) chain of events
• MC API can be successfully queried via the API GW URL, and returns health Check JSON that's stored in the S3 bucket.
• The UI/UX "UI Navbar" component is happily able to request this data via the MC API

[GodwinShen]

@jdrodjpl and @galenatjpl ping for status update

[jdrodjpl]

Making good progress, have the MC backend querying for the parameter and getting the values, just working now on the JSON output. On track for completion early next week.

[GodwinShen]

@jdrodjpl ping for status, is this still on track for early this week?

[jdrodjpl]

So far, the only hitch (which I didn't realize) is that we don't yet have health check data being populated to the bucket. I'm working with @hargitayjpl to get the correct bucket created and populated with data so I can ensure that the end-to-end process is working.

[GodwinShen]

@jdrodjpl ping for status.

[galenatjpl]

@jdrodjpl Do you think you and @hargitayjpl can give a quick status update and/or demo tomorrow, on 6/4 about where everything is currently at?