mcm-apigw

Deploys API gateway v2 instance for HTTP APIs.

During initial deploy, Certificate Manager will need to be accessed in order to add Route 53 records to confirm certificate (deploy will stall and ultimately time out if this is not done).

NOTE: Once deployed, the name for the application envirionment must be set by setting the /mcm-v1/service/name SSM parameter in the account (and in the appropriate region - us-east-2, by default), to type String and the appropriate value (usually 'Mirific Systems - ', or 'Mirific Systems' for production).

Dependencies

This stack requires that the mcm-app infrastructure has been properly deployed (see https://github.com/MCMLLC/mcm-infrastructure/blob/develop/mcm-apps/README.md). In addition, the folllowing stacks must be present:

• mcm-cognito

Standard named lambda functions published by this stack

Lambda name	Definition

Standard exported symbols to be used by apps within the given account

Symbol	Definition
mcm-apigw-gatewayId	ID of API Gateway V2 provided
mcm-apigw-URL	URL of custom domain name for API Gateway
mcm-apigw-Authorizer	ID of gateway authorizer tied to Cognito and the provided gateway

Standard SSM Parameters published by this stack

Symbol	Definition
/mcm-v1/service/name	Friendly name for service instance
/mcm-v1/service/id	Instance ID of service (same as mcm-app-envID export)
/mcm-v1/service/apiURL	Direct API URL for API gateway
/mcm-v1/service/subdomain	Subdomain name (same as mcm-app-dnszone-HostedZoneName export)

Stack removal

No special considerations.