Skip to content

Releases: cloudposse/terraform-aws-cloudfront-s3-cdn

v0.75.0

24 Aug 12:59
47d70f2

Choose a tag to compare

Enable compression of responses by default @alexjurkiewicz (#173)

Compression of responses is free, and should always be a net-positive.

v0.74.3

21 Aug 05:21
cc56b64

Choose a tag to compare

🤖 Automatic Updates

Update Terraform cloudposse/s3-log-storage/aws to v0.24.1 @renovate (#170)

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-log-storage/aws (source) module minor 0.20.0 -> 0.24.1

Release Notes

cloudposse/terraform-aws-s3-log-storage

v0.24.1

Compare Source

🤖 Automatic Updates

Update context.tf @​cloudpossebot (#​59) #### what This is an auto-generated PR that updates the `context.tf` file to the latest version from `cloudposse/terraform-null-label` #### why To support all the features of the `context` interface.

v0.24.0

Compare Source

Add variable access_log_bucket_prefix to customize S3 access log configuration @​adamantike (#​57) #### What Allow changing the prefix to be used in the specified S3 bucket for access logs. Maintain current prefix as default value, for backwards compatibility. #### Why This is useful for projects using different standards (e.g. path with bucket name in the root folder).

v0.23.0

Compare Source

add allow_ssl_requests_only flag @​mcalhoun (#​56) #### what

why

  • There was a missing data "aws_partition"

v0.22.0

Compare Source

add allow_ssl_requests_only flag @​mcalhoun (#​55) #### what
  • Add the allow_ssl_requests_only flag to force the bucket to be accessed via TLS only

why

  • AWS Foundational Security Best practices indicate S3 buckets should require requests to use Secure Socket Layer

references

v0.21.0

Compare Source

added versioning mfa delete enabled option @​chafnan (#​54) #### what This adds the option to turn on MFA Delete for the bucket. * 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 issue #​48 does a good job explaining, but pasted important information below

Security best practices for CloudTrail logs that are stored in S3 recommend MFA Delete be enabled.
https://www.cloudconformity.com/knowledge-base/aws/CloudTrail/cloudtrail-bucket-mfa-delete-enabled.html

references

closes #​48


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.74.2

21 Aug 04:58
47e337d

Choose a tag to compare

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.25.0 @renovate (#180)

This PR contains the following updates:

Package Type Update Change
cloudposse/label/null (source) module minor 0.24.1 -> 0.25.0

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132) ##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module
Fix: Update README Snippets @​korenyoni (#​130) ##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A
Bridgecrew compliance @​Nuru (#​125) ##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.74.1

21 Aug 03:20
6d38404

Choose a tag to compare

🤖 Automatic Updates

Update context.tf @cloudpossebot (#181)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.74.0

01 Aug 03:10
ce3f377

Choose a tag to compare

Add trusted_* vars per ordered_cache @martinlindner (#176)

what

Add individual trusted_signers, trusted_key_groups attributes to var.ordered_cache.

why

  • "Private content" / signature checks should be configurable on a per-behavior level instead of just enforcing the global settings for all.

v0.73.0

02 Jul 19:27
138e146

Choose a tag to compare

Feat: Add Support for Origin Groups (Failover Origins) @korenyoni (#174)

what

  • Add Support for Origin Groups (failover origins)
  • Add tests for var.s3_origins and var.custom_origins
  • Add functionality such that if s3_origin_config.origin_access_identity in var.s3_origins is null or an empty string, translate it to the origin_access_identity used by the origin created by the module.

why

  • Certain CloudFront distributions require origins to be backed by failover origins. This can only be done using Origin Groups, which prior to this PR is not supported by the module.
  • The variables var.s3_origins and var.custom_origins were not tested using the test suite.

references

v0.72.1

28 Jun 15:08
f5169df

Choose a tag to compare

🚀 Enhancements

Fix README Snippet Use of `deployment_principal_arns` @korenyoni (#172)

what

  • Fix use of deployment_principal_arns variable in README snippet.

why

  • The IAM Role ARN supplied in the deployment_principal_arns map is actually using S3 ARNs. This fixes the ARNs such that they are IAM Role ARNs.

references

  • N/A

v0.72.0

10 Jun 15:32
48ac13a

Choose a tag to compare

add allow_ssl_requests_only to force ssl communication @mcalhoun (#171)

what

  • Add the allow_ssl_requests_only flag to force the s3 bucket to only communicate over ssl

why

  • AWS Foundational Security Best Practices

v0.71.0

01 Jun 13:06
4082eb2

Choose a tag to compare

Add trusted_key_groups @yangroro (#168)

what

  • Add trusted_key_groups variable
  • Add trusted_key_groups to cloudfront cache behavior

references

I cannot find makefile guide. So, let me notice something is wrong. I will response quickly as I can.

v0.70.0

31 May 16:15
fc8ca0d

Choose a tag to compare

Add support for a custom cache policy for ordered cache @linhkikuchi (#169)

what

  • To add support for a custom cache policy for ordered cache