3.5.4

1. Update lambda version to nodejs18.x

3.5.3

remove all FOS version support prior to 7.2.2

3.5.2

update supported FortiOS versions in deployment templates.

FOS: (+)6.4.9, 7.2.1 (-)6.4.8, 6.4.7, 7.0.3, 7.0.2
FAZ: (+)7.2.0, 6.4.8, 6.4.7

3.5.1

update supported FortiOS and FortiAnalyzer versions in deployment templates.

FOS: 7.0.3, 7.0.2, 6.4.8, 6.4.7
FortiAnalyzer: 6.4.7

3.5.0

related project: https://github.com/fortinet/fortigate-autoscale-aws/projects/2

summary:

Added
[enhancement] heartbeat calculation improvement based on heartbeat request sequence and timestamp
[enhancement] improve primary election facilitating the device sync info
Changed
[bugfix] a brand new vm elected as the new primary will lead to existing configuration loss

3.4.1

bugfix:
#71 Python 2.7 deprecated
#48 increased default Lambda memory size to 256MB

3.4.0

1. by a new feature toggle, it allows to keep unhealthy vms in the autoscaling group in 'out-of-sync' state and to recover into 'in-sync' (new default behaviour) or to terminate them (old default behaviour).

2. added AWS SNS integration for late heartbeat notifications and unhealthy vm detection notifications.

3. resolved issues: #65 #61 #60 #56 #55 #53 #52

4. update to the new Autoscale Core (3.3.0) that resolved a few heartbeat monitor related bugs. see the autoscale-core 3.3.0 release for details.

3.3.2

update FOS and FAZ support versions (including us-gov cloud)

FOS: + 7.0.0, + 7.0.1, - 6.2.3, - 6.4.4
FAZ: + 6.4.6, - 6.2.5, - 6.4.4

3.3.1

resolved the VPC Endpoint conflicts when deploying multiple FortiGate Autoscale into one VPC.

issue: #43

3.3.0

US Gov cloud support