v3.0.3

What's Changed

• Fix revalidation_function reporting a state change by @Maddog2050 in #36
• Move s3 assets below server functions and additional origin. The default route has been configured to remain the last route in each zone. This fixes issue #37

New Contributors

• @Maddog2050 made their first contribution in #36.

Full Changelog: v3.0.2...v3.0.3

v3.0.2

Remove the use of one function when determining lambda permissions
When combined with the try function, this caused Terraform to mark the result as computed when using Terraform v1.5.7
This doesn't affect Terraform v1.6.1 or above however, the change was made to allow some capability with older versions of Terraform

Fix issue where the script didn't correctly sync objects which contained spaces in the file path
Special thanks to @heftyzauk for identifying and fixing the issue.

v3.0.1

Update precedence order to push image optimisation before static assets.
Prior to this change. The image optimisation failed with an access denied error.

Special thanks to @adatoo for identifying and fixing the issue.

v3.0.0

Support for Open Next V3 🎉 🚀

Version 3 of the module supports many of the features released as part of Open Next v2 and V3, including:

• Support for function splitting
• Support for external middleware (Only Lambda@edge is supported)
• Support for open-next.output.json configuration file
• Support for server actions
• Support for ISR revalidation
• Support for Image Optimisation

NOTE: Open Next v3 introduced additional deployment targets. This module only supports hosting resources in lambda and lambda@edge; running resources on Cloudflare, ECS, etc., is not supported.

Where possible, the modules try to give you as many configuration options as possible; however, the module won't be able to cater to all use cases. For the majority of components, you can curate your bespoke resources in Terraform, i.e. WAF, CloudFront distribution, etc., and pass the ARN of the resource to the module to use.

Upgrading

From 2.x to 3.x

The module has been made backwards compatible with 2.x where possible.

For open next v3, the module will read the open-next.output.json file in the .open-next directory to determine the edge and server functions that need to be configured, as well as any default configuration, e.g., streaming.

NOTE: Deprecated fields have been removed. If you use one of the following values, you will need to modify your Terraform/ Terragrunt configuration

• The EDGE_LAMBDA backend deployment type is no longer supported for server function. In open next v3, this has been moved into edge functions instead [BREAKING CHANGE]
• aws_lambda_permission.server_function_url_permission and aws_lambda_permission.image_optimisation_function_url_permission have been merged into a list of aws_lambda_permission.function_url_permission resources in the tf-aws-open-next-multi-zone module. You can either let the resources re-create or update the references using either move config, import block or import command [BREAKING CHANGE]
• CloudFront cache policy ARN - you must now set the CloudFront Cache Policy ID
• Auth function CloudFront log group - this configuration had no effect, so it has been removed
• Lambda Logging configuration (for regional lambda's only) [NEW FEATURE]
• Additional configuration of CloudWatch log groups, including having a log group for all regional functions in a zone [NEW FEATURE]

If you are still using open next v2.x, you can set the open_next_version variable to v2.x.x (the default value). If you upgrade to Open Next v3.x, please set the open_next_version variable to v3.x.x.

If you want to migrate from Open Next v2 to v3, see the migration guide, which the Open Next team created.

v2.4.1

fix: correct issue where permissions were set on the server function and not image optimisation function

v2.4.0

feat: add the ability to use origin access control (oac) with lambda urls

CloudFront have added support for lambda urls on origin access control (oac)

Note: the minimum version of the AWS terraform provider has been bumped to 5.46.0, to upgrade your .terraform.lock.hcl please run either terraform init -upgrade or terragrunt init -upgrade

Documentation has been improved to highlight possible configuration options for the inputs on both multi-zone and single-zone deployments

v2.3.0

feat: add the ability to configure www subdomain and overwrite route53 records

Added additional documentation to cover the possible configuration options for custom domains

v2.2.2

fix: add additional permissions for the server function to read and write data to dynamodb
Also adds extra permissions for sqs.
These permissions are based upon permissions assigned via the nextsite CDK construct and ion implementations

fix: issue where the data being saved to dynamo was not in the correct format

The alias saved to the dynamo table needs to have the data type of string specified
Omit tf_key from the database

v2.2.0

feat: add streaming support for the server function