Deploys API gateway v2 instance for cross-environment deep links redirect
Before initial deploy, the following fields will need to be set in the us-east-2 SSM parameter store for the MCMDirectory account:
- Name: /mcm-v1/links/android-sha256-cert-fingerprints Type: StringList Value: comma separated list of sha245-cert-fingerprints for Android apps
- Name: /mcm-v1/links/ios-appids Type: StringList Value: list of appIDs for iOS ('teamID.packageName') (e.g. '7V3F5V94C9.com.mirificsystems.mobile')
- Name: /mcm-v1/links/android-packagename Type: String Value: Team ID for Android app (e.g. '7V3F5V94C9')
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).
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).
It also depends upon a second public DNS zone being deployed, using the following:
- Deploy zone-public.yml with the following parameter values: Stack Name of mir-links-dnszone Name set to links.mirificsystems.com
| Lambda name | Definition |
|---|
| Symbol | Definition |
|---|---|
| mcm-apigw-directory-gatewayId | ID of API Gateway V2 provided |
| mcm-apigw-directory-URL | URL of custom domain name for API Gateway |
| Symbol | Definition |
|---|---|
| /mcm-directory/service/name | Friendly name for service instance |
| /mcm-directory/service/id | Instance ID of service (same as mcm-app-envID export) |
| /mcm-directory/service/apiURL | Direct API URL for API gateway |
| /mcm-directory/service/subdomain | Subdomain name (same as mcm-app-dnszone-HostedZoneName export) |
No special considerations.