Releases: milliHQ/terraform-aws-next-js
v1.0.0-canary.1
First prerelease for the multiple deployments feature.
v0.9.2
⚠️ Namespace changed ⚠️
We recently changed the namespace of this module from dealmore
to milliHQ
. Make sure to upgrade the source of the module accordingly:
module "tf_next" {
- source = "dealmore/next-js/aws"
+ source = "milliHQ/next-js/aws"
...
}
Changelog
Besides from the namespace change, this release has now an improved experience when using it with custom domains and some bugfixes to the proxy component when using the trailingSlash
option from Next.js.
Terraform module
- It's now possible to use domain aliases without creating an external CloudFront distribution (#192)
- Ensure
x-nextjs-page
header gets forwarded (#190) - Bump
milliHQ/download/npm
from 1.1.0 to 2.0.0 (#193)
Proxy (0.8.0)
v0.9.1
This is a maintenance release which upgrades the image optimizer module to the latest version.
We also changed the behavior of the proxy module so that the default root object in CloudFront is no longer necessary.
No configuration changes should be necessary when upgrading from the 0.9.0
release.
Changelog
Terraform module
- Upgrades Proxy component to 0.7.0 (#139, #141)
- Upgrades Terraform Next.js Image Optimization module for AWS to
11.x.x
release (#142, #144)
The image optimizer Lambda now uses2048mb
RAM by default (from1024mb
) to improve resizing speed.
You can change that amount with the newly introduced variableimage_optimization_lambda_memory_size
.
This has no effect on the Lambda functions that serve the Next.js pages or api routes (they remain at1024mb
by default). - Bump AWS Lambda Terraform module from 1.47.0 to 2.4.0 (#145)
- Bump AWS API Gateway Terraform module from 0.11.0 to 1.1.0 (#146)
Proxy (0.7.0)
v0.9.0
Changes for CloudFront customization
Since the main CloudFront distribution is a central resource that may need advanced customization, we decided to introduce a new way to fully customize the distribution for to your needs.
As part of this change a few input variables are no longer supported and should be removed from the module.
If you are not using one of these variables you can safely upgrade to this release without further changes.
If you use one of the following input variables read below for more information how to upgrade:
cloudfront_custom_behaviors
cloudfront_geo_restriction
cloudfront_origins
cloudfront_viewer_certificate_arn
cloudfront_minimum_protocol_version
create_domain_name_records
domain_names
domain_zone_names
If you are already using one of these input variables you should now create a new CloudFront resource in your main.tf
file and link it with the Next.js module.
For more information please see the "with existing CloudFront" and "with custom domain" examples.
Changelog
Terraform module
- Enable usage of external CloudFront resource (#55, #134, #137)
- Queue CloudFront invalidations (#48, #125)
- Attaching Lambda to VPC (#110, #111)
Thanks to @chamilad for contributing! - Remove provider proxy from proxy-config module (#102, #124)
Proxy (0.6.0)
Deploy trigger (0.4.0)
v0.8.1
v0.8.0
This release enables Brotli in addition to gzip as default compression method.
Before upgrading make sure that you define a new alias global_region
for the AWS Provider in the us-east-1
region.
This provider alias is used to create the Lambda@Edge function that must be created in us-east-1
.
# main.tf
provider "aws" {
region = "us-west-2"
}
+ provider "aws" {
+ alias = "global_region"
+ region = "us-east-1"
+ }
module "tf_next" {
source = "dealmore/next-js/aws"
+ providers = {
+ aws.global_region = aws.global_region
+ }
}
Changelog
Terraform module
- Removes internal AWS provider for
us-east-1
region (#50, #101) - Enable Brotli compression for CloudFront (#8, #82)
- Adds
cloudfront_geo_restriction
variable (#97) - Use
nodejs14.x
as default runtime for Lambda (#67, #80, #81)
Deploy trigger (0.3.0)
- CloudFront invalidations for static files (e.g. static prerendered HTML or files from
public/
) are only issues if the eTag of the file changes (#48, #91)
tf-next (0.6.1)
- Ensure that
INIT_CWD
environment variable is set to the correct working directory (#87)