v0.4.3

Exposes Lambda function architectures.

What's Changed

• Expose Lambda function architectures by @bwhaley in #71

The Terraform module now accepts var.architectures to configure whether to use arm64 or x86_64.

Thanks to @n-tucker for the contribution.

Full Changelog: v0.4.2...v0.4.3

v0.4.2

Adds a new input, nat_instance_user_data_post_install, that can contain a script to run on NAT instances at boot time after alternat is configured. Many thanks to @eddycek for this contribution!

What's Changed

• Add support for installing third party software on EC2 by @eddycek in #63

New Contributors

• @eddycek made their first contribution in #63

Full Changelog: v0.4.1...v0.4.2

v0.4.1

• Adds a new output, nat_instance_security_group_id
• Adds a new variable, nat_instance_block_devices, to customize the block devices on alternat instances.

Many thanks to @Halama and @irasnyd for these contributions!

What's Changed

• docs: fix typos by @oponomarov-tu in #54
• Clarify alterNAT value prop in the README by @bwhaley in #58
• Adds optional EBS volume customization by @bwhaley in #57
• Output NAT Instance Security Group by @irasnyd in #61

New Contributors

• @irasnyd made their first contribution in #61

Full Changelog: v0.4.0...v0.4.1

v0.4.0

This update removes the dependency on the python requests library from the replace-route function and replaces it with the native urllib. alterNAT can now be deployed using AWS Lambda Python runtime which by default has all the required third-party dependencies preinstalled (boto3).

The alternat_image_* inputs are now optional. Nothing has changed for the Docker image runtime which remains the default deployment scenario.

Many thanks to @jgr-trackunit and @oponomarov-tu for this contribution!

v0.3.3

Moves some noisy log messages to debug level.

v0.3.2

Allows the user to optionally disable the creation and management of NAT Gateways by alterNAT by setting create_nat_gateways=false. When set, The user can manage NAT gateways separately - within the vpc module, for example - and alterNAT will work with those rather than provision its own.

When using create_nat_gateways=false, you must allow alterNAT to manage the 0.0.0.0/0 route. That is, do not use an aws_route resource for the NAT Gateway with 0.0.0.0/0 as a destination. alterNAT expects to be able to manage the route on its own using the NAT instance userdata script and the replace-route Lambda function. You can either remove the aws_route resource from your configuration or set:

  lifecycle {
    ignore_changes = all
  }

on the resource to ensure that Terraform ignores it.

v0.3.1

Adds support for VPCs with multiple CIDR block associations.

v0.3.0

Adds support for native lambda deployments. You can now pass lambda_package_type = "Image (the default) to use a container image, or lambda_package_type = Zip to use a zip file.

Thanks to @oponomarov-tu for this contribution!

v0.2.1

Replaces the template_cloudinit_config resource introduced in v0.2.0 with cloudinit_config to avoid a dependency on the deprecated template provider.

v0.2.0

This update includes backwards incompatible changes. Follow the migration guide to update without downtime for existing NAT instances.

This update includes a few important changes:

• Modifies the userdata and Lambda function inputs for compatibility with other IaC tooling such as CDK that cannot use Terraform template style.
• Allows multiple sets of private subnets/route tables. Previously it was only possible to include one set of private route tables and subnets within a VPC.
• Exposes the Auto Scaling Group Lifecycle hook heartbeat timeout value.
• Eliminates the dependency on a particular naming convention for private subnets. Subnets are now passed explicitly, so we don't need to discover them by name.