feat: Cloudwatch Synthetic Canary and Alarm for /metadata endpoint

[Zambonilli]

Issue #, if available:

Description of changes: Addition of a cloudwatch synthetic for calling the /metadata endpoint and an associated alarm that is raised on failure. Cloudwatch synthetic calls the /metadata endpoint for a stage every 15 minutes and looks for a 2** HTTP status code for success. Cloudwatch alarm looks at the synthetic's Failed metric and raises the alarm if any synthetic fails.

Checklist:

• [X] Have you successfully deployed to an AWS account with your changes?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[Zambonilli]

@Bingjiling Apologies on how long it took to get this wrapped up. I was able to create a generic convention for building synthetics and having them uploaded via a new custom cloudformation resource. There is a new synthetics directory, cloudformation yaml and README.md explaining how to build new synthetics.

Let me know if you have any questions or concerns.

[codecov-commenter]

Codecov Report

Merging #391 (3a3ebaf) into develop (15be319) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #391   +/-   ##
========================================
  Coverage    91.42%   91.42%           
========================================
  Files            8        8           
  Lines          280      280           
  Branches        47       47           
========================================
  Hits           256      256           
  Misses          23       23           
  Partials         1        1           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 15be319...3a3ebaf. Read the comment docs.

[Zambonilli]

Not sure why github is flagging the feature/synthetics_pr as having conflicts in package.json & serverless.yaml when the conflicts have been resolved in the branch already. I tried using the github UI to resolve the conflicts by matching the code in the feature branch but even the github UI is returning an error saying the screen is out of sync. Let me know if I'm missing something here and I'll update the feature/synthetics_pr branch to kick github's conflict detection.

[Zambonilli]

Pushed an update to the latest puppeteer runtime and it resolved the conflicts. Not sure why github got tripped up but it looks to be resolved now.

[nisankep]

FHIR Works on AWS has been moved to maintenance mode. While in maintenance, we will not add any new features to this solution. All security issues should be reported directly to AWS Security at [[email protected]] (mailto:[email protected]). If you are new to this solution, we advise you to explore using [HealthLake] (https://aws.amazon.com/healthlake), which is our managed service for building FHIR based transactional and analytics applications. You can get started by contacting your AWS Account team. If you are an existing customer of FHIR Works on AWS, and have additional questions or need immediate help, please reach out to [email protected] or contact your AWS Account team.