The deployment guide documentation says to set the "network tags" in the Meraki Dashboard to "vMX-1" and "vMX-2", but in Table 1 lower down, and more crucially as a pre-populated parameter in the CloudFormation template, the tags are set to "vMX1" and "vMX2".
As these tags are used as environment variables in the Lambda job that is executed to fail over the routing, this discrepancy causes the job to fail until corrected, so the documentation should be changed to make it consistent with the table and CFT.
The deployment guide documentation says to set the "network tags" in the Meraki Dashboard to "vMX-1" and "vMX-2", but in Table 1 lower down, and more crucially as a pre-populated parameter in the CloudFormation template, the tags are set to "vMX1" and "vMX2".
As these tags are used as environment variables in the Lambda job that is executed to fail over the routing, this discrepancy causes the job to fail until corrected, so the documentation should be changed to make it consistent with the table and CFT.