v0.10.3

What's Changed

• Bugfix with the cloudwatch-agent installation by @Alex-BrightD in #161

New Contributors

• Many thanks to @Alex-BrightD for their first contribution in #161

Full Changelog: v0.10.2...v0.10.3

v0.10.2

What's Changed

• Bumps required Terraform version by @bwhaley in #157
• Use the name prefix for Launch Templates by @p8r-the-gr8 in #158

Alternat launch templates will now be more identifiable. Thanks for another improvement, @p8r-the-gr8!

Full Changelog: v0.10.1...v0.10.2

v0.10.1

What's Changed

• Add option to install and configure CloudWatch Agent by @p8r-the-gr8 in #155

Thanks @p8r-the-gr8 for this feature!

v0.10.0

What's Changed

• Bump github.com/hashicorp/go-getter from 1.7.5 to 1.7.9 in /test by @dependabot[bot] in #149
• Bump golang.org/x/oauth2 from 0.8.0 to 0.27.0 in /test by @dependabot[bot] in #144
• Minor updates to README.md by @bwhaley in #150
• Fix example and warnings by @p8r-the-gr8 in #152
• Always use the latest AMI by @p8r-the-gr8 in #153
• Install SSM Agent when enable_ssm=true by @p8r-the-gr8 in #154

Improvements from @p8r-the-gr8

• Updates the launch template to always use the latest AMI using the resolve feature.
• Switches to the Amazon Linux 2023 minimal AMI.
  Thanks for this contribution!

Full Changelog: v0.9.3...v0.10.0

v0.9.3

What's Changed

• get_nat_gateway_id: Only consider available nat gateways by @Jasper-Ben in #146
• Treat all http codes < 500 as success by @Jasper-Ben in #147
• fix: add conntrack-tools by @hak891 in #148

Many thanks to @Jasper-Ben and @hak891 for these improvements.

Full Changelog: v0.9.2...v0.9.3

v0.9.2

Thanks to these contributors!

• @hak891 made their first contribution—fix: add missing volume tags propagation in #142
• fix: unable to create IAM policy when AlterNAT is deployed in several regions by @franck-dailymotion in #141

Also:

• Bump golang.org/x/net from 0.23.0 to 0.36.0 in /test by @dependabot[bot] in #128
• Bump go.mod by @bwhaley in #143

Full Changelog: v0.9.1...v0.9.2

v0.9.1

What's Changed

• Makes SSM command permissions optional based on nat restore by @bwhaley in #140

Full Changelog: v0.9.0...v0.9.1

v0.9.0

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:

0. Assume that the connectivity check has failed and the route was updated to use the NAT Gateway.
1. During the next connectivity check, attempt to restore the NAT instance
2. Send an SSM command to curl the connectivity check URLs
3. If the connection is successful, check the NAT configuration
4. If the configuration is correct, update the route to use the NAT instance.
5. 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

v0.8.7

What's Changed

• fix: avoid empty eip ids when prevent_destroy_eips is enabled by @franck-dailymotion in #136

Many thanks to @franck-dailymotion for this contribution!

v0.8.6

What's Changed

• Reverts deprecated aws_region change for compatibility with v5 by @bwhaley in #134

Full Changelog: v0.8.5...v0.8.6