LambdaAA-RouteFailover/6.0/FGT_LambdaAA-RouteFailover_ExistingVPC_BYOL.template.json Lambda function - python.3.8 FGT v6.2.3 build8404
Successful deployment with modified "fgtami" values in template file, API keys also proper.
When FGT1 is stopped from EC2, FGT1-private route table goes to "blackhole", instead of automatically updating to FGT2-private-eni as per the template.
On FGT -> Automation -> Create Automation Stitch -> Name: "health-check" -> Trigger FortiOS Event Log -> Event: Link Monitor Status -> Action AWS Lambda -> 1st Action Name: "healthcheck-action" -> API Gateway, API Key, ID, Region, etc... are correct.
Template
LambdaAA-RouteFailover/6.0/FGT_LambdaAA-RouteFailover_ExistingVPC_BYOL.template.json
Lambda function - python.3.8
FGT v6.2.3 build8404
Successful deployment with modified "fgtami" values in template file, API keys also proper.
When FGT1 is stopped from EC2, FGT1-private route table goes to "blackhole", instead of automatically updating to FGT2-private-eni as per the template.
On FGT -> Automation -> Create Automation Stitch -> Name: "health-check" -> Trigger FortiOS Event Log -> Event: Link Monitor Status -> Action AWS Lambda -> 1st Action Name: "healthcheck-action" -> API Gateway, API Key, ID, Region, etc... are correct.