When using BYOL licensing, the ImageFunction is returning an AMI ID for the "Fortinet Federal FortiGate (BYOL) Next-Generation Firewall" (https://aws.amazon.com/marketplace/pp/prodview-y7diw5udavvhy). Since customers subscribed to the Fortinet BYOL listing, this produces an error in launching the template. Further, the Federal offering does not support c5.size instances, so if you go ahead and subscribe to the Fortinet Federal listing, half the instance choices do not work with it.
I haven't looked into region availability of the Fortinet Federal listing, I just confirmed that the ImageFunction is mapping to the Federal listing in us-west-1 specifically. Other regions may be affected. Confirmed this behavior for 7.4.x, both dualAZ and singleAZ.
Desired outcome: HA cloudformation templates should launch AMI's associated with the Fortinet FortiGate BYOL listing.
When using BYOL licensing, the ImageFunction is returning an AMI ID for the "Fortinet Federal FortiGate (BYOL) Next-Generation Firewall" (https://aws.amazon.com/marketplace/pp/prodview-y7diw5udavvhy). Since customers subscribed to the Fortinet BYOL listing, this produces an error in launching the template. Further, the Federal offering does not support c5.size instances, so if you go ahead and subscribe to the Fortinet Federal listing, half the instance choices do not work with it.
I haven't looked into region availability of the Fortinet Federal listing, I just confirmed that the ImageFunction is mapping to the Federal listing in us-west-1 specifically. Other regions may be affected. Confirmed this behavior for 7.4.x, both dualAZ and singleAZ.
Desired outcome: HA cloudformation templates should launch AMI's associated with the Fortinet FortiGate BYOL listing.