Releases: cloudposse/terraform-aws-cloudfront-s3-cdn
Releases · cloudposse/terraform-aws-cloudfront-s3-cdn
0.29.0: Add existing cloudfront origin access identity (#93)
* Update main.tf * cloudfront_origin_access_identity_path * Update variables.tf * Updated README.md Co-authored-by: actions-bot <[email protected]>
0.28.0
0.27.0: Fix log version error (#89)
Co-authored-by: Joe Niland <[email protected]>
0.26.0: feat: Allow specifing custom origins (#78)
what
- allow specifing/creating (additional) custom origins
why
- This module is really useful for front-end website deployments but sometimes it is required to use the same domain for front-end and back-end (different paths) or add some back-end functionality to front-end website without creating real back-end
- To configure API Gateway easily
- We already have the ability to configure
ordered_cache_behaviourso we technically support multiple strategies for different paths
references
example usage
module "cloudfront-s3" {
# ...
ordered_cache = [{
target_origin_id = "api-gateway-with-lambda"
path_pattern = "/v1/lambda"
allowed_methods = ["HEAD", "GET"]
cached_methods = ["HEAD", "GET"]
compress = true
viewer_protocol_policy = "redirect-to-https"
min_ttl = 0
default_ttl = 60
max_ttl = 3600
forward_header_values = []
forward_query_string = true
forward_cookies = "none"
lambda_function_association = []
}]
custom_origins = [{
domain_name = "xxxxxxxxxx.execute-api.us-east-1.amazonaws.com"
origin_id = "api-gateway-with-lambda"
origin_path = null
custom_origin_config = {
http_port = 80
https_port = 443
origin_protocol_policy = "https-only"
origin_ssl_protocols = ["TLSv1.2"]
origin_keepalive_timeout = 5
origin_read_timeout = 30
}
}]
}0.25.0: Update bucket logging module version (#82)
what
- Add compatibility with the latest label module's version
why
- s3 bucket module has the same name in different environment
0.24.0: Fixes issue with multiple `cors_allowed_origins`
what
- We now dynamically generate the cors rules block so we correctly create a block for each alias/allowed origin.
why
- CORS origins don't work without these changes
- I believe this change makes them work as intended in the original module
references
- Closes #22
0.23.2: Fix tests to use randomized bucket name
0.23.1 Fix `trusted_signers` in ordered cache
what
- Fix
trusted_signersin ordered cache
why
- bug with wrong value expression
0.23.0 Make it optional to override the origin s3 policy
what
- Make it optional to override the origin s3 policy
why
- When specifying
var.origin_bucket, it can be nice to leave the existing bucket's policy as is. For example, when manage an s3 bucket that multiple CloudFront dists use as their origin (without paths, they just use the same code). In this case, we may not want to restrict the bucket to only talk to a single CF dist, as this module does by default.