What's Changed
- New feature: Failback to NAT instance by @franck-dailymotion in #137
- Adds tests for NAT instance recovery by @bwhaley in #139
NAT instance recovery feature
Many thanks to contributor @franck-dailymotion for this new feature! 🎉
If the route has previously been updated to use the standby NAT gateway due to a health check failure, the replace-route function can optionally attempt to detect recovery of the NAT instance. This allows the system to automatically recover and return to the preferred, cost-effective path of the NAT instance as soon as it is healthy.
This feature is disabled by default. To enable it, set enable_nat_restore=true and enable_ssm=true.
How it works:
- Assume that the connectivity check has failed and the route was updated to use the NAT Gateway.
- During the next connectivity check, attempt to restore the NAT instance
- Send an SSM command to curl the connectivity check URLs
- If the connection is successful, check the NAT configuration
- If the configuration is correct, update the route to use the NAT instance.
- Continue with regular connectivity checks through the NAT instance.
Note that the route recovery feature does not attempt to remediate any configuration issue on the instance; the instance remains immutable.
Full Changelog: v0.8.7...v0.9.0