what

• Add an optional fixed response to the default auction of the listener (http or https).

why

• I have a case where I am using a Cloudfront distribution that passes a special header to verify the validity of the request (as described here https://www.arhs-group.com/protecting-aws-alb-behind-aws-cloudfront-distribution/). I want to use a listener rule to respond with a 403 if that header is missing or incorrect. Since the module always forwards to the TG unconditionally, I am adding this feature as an alternative.

what

• Add Terraform 0.14 support
• Use new syntax in main.tf/versions.tf

why

• This module needs to support Terraform 0.14

what

• Adding SNI support

why

• variable was added but the resource was missing

what

• Enable SNI support for https listener when https listener is enabled

why

• many times an alb is reuse for multiple urls and with SNI support we can attach multiple certs to the same listener

references

• https://aws.amazon.com/blogs/aws/new-application-load-balancer-sni/

what

• Allows the specification of a health check port that is not the traffic-port.

why

• The health check endpoint doesn't necessarily always exist on the default traffic-port, as is my case.

what

• Bump the tag for s3 bucket module to use >= 2.0 for aws provider to avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).
• Bump the tag to 0.21.0 for terraform-null-label module to support future versions of TF.

why

• This module is being used with terraform-aws-eks-node-group which needs aws provider version to be >= 2.0 to fix version conflicts.

references

• See cloudposse/terraform-aws-eks-node-group#41 for details. This tackles one of the modules causing the issue.

what

• Update to context.tf.

why

• In v0.19.0 the enabled var was added manually instead of via context.

references

• Refs #56

what

This allows the ALB to be created selectively.

why

As a cost saving measure, I want to be able to create an ALB per AWS account for a given application and then create multiple target groups.

references

• This addresses #55.

The aws = ~> 2.0 causes error in Terraform 0.13:

Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/aws:
no available releases match the given constraints >= 3.0.*, >= 2.0.*, >=
2.0.*, >= 2.0.*, >= 2.0.*, >= 2.0.*, < 4.0.*, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0,
~> 2.0, ~> 2.0, >= 2.0.*, < 4.0.*, >= 3.0.*, >= 2.0.*, >= 2.0.*, >= 2.0.*

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

what

• module access_logs is using tagged version that has issues with TF 0.13, so updating to use a fixed version of that module

why

• this module currently fails with TF 0.13, and has no tests for TF 0.13 to automatically detect these issues