Update Terraform cloudposse/s3-log-storage/aws to v1 (release/v0)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-log-storage/aws (source)	module	major	`0.28.3` -> `1.4.2`

Release Notes

cloudposse/terraform-aws-s3-log-storage (cloudposse/s3-log-storage/aws)

### [`v1.4.2`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.4.2) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.4.1...1.4.2) #### 🚀 Enhancements

Add `grants` input @Nuru (#93)

#### what - Add `grants` input #### why - Some AWS services, such at Cloudfront, require specific grants for log delivery #### references - [Cloudfront log delivery requirements](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html#AccessLogsBucketAndFileOwnership)

### [`v1.4.1`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.4.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.4.0...1.4.1)

Sync .github @max-lobur (#89)

Rebuild '.github' dir from the template

#### 🚀 Enhancements

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @renovate (#91)

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudposse/s3-bucket/aws](https://registry.terraform.io/modules/cloudposse/s3-bucket/aws) ([source](https://togithub.com/cloudposse/terraform-aws-s3-bucket)) | module | patch | `3.1.1` -> `3.1.2` | *** ##### Release Notes

cloudposse/terraform-aws-s3-bucket

##### [`v3.1.2`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.2): Fix Public Bucket Creation [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.1...3.1.2) ##### What's Changed - Remove reference to TF_DATA_DIR retained by mistake in [#40](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/40) by [@Nuru](https://togithub.com/Nuru) in [https://github.com/cloudposse/terraform-aws-s3-bucket/pull/181](https://togithub.com/cloudposse/terraform-aws-s3-bucket/pull/181) - Sync .github by [@max-lobur](https://togithub.com/max-lobur) in [https://github.com/cloudposse/terraform-aws-s3-bucket/pull/183](https://togithub.com/cloudposse/terraform-aws-s3-bucket/pull/183) - Fix linters / Retest on AWS provider V5 by [@max-lobur](https://togithub.com/max-lobur) in [https://github.com/cloudposse/terraform-aws-s3-bucket/pull/188](https://togithub.com/cloudposse/terraform-aws-s3-bucket/pull/188) - Fix Public Bucket Creation by [@rankin-tr](https://togithub.com/rankin-tr) in [https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194](https://togithub.com/cloudposse/terraform-aws-s3-bucket/pull/194) ##### New Contributors - [@rankin-tr](https://togithub.com/rankin-tr) made their first contribution in [https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194](https://togithub.com/cloudposse/terraform-aws-s3-bucket/pull/194) **Full Changelog**: https://github.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.1...3.1.2

***

#### 🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @renovate (#91)

cloudposse/terraform-aws-s3-bucket

***

### [`v1.4.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.4.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.3.1...1.4.0) - No changes ### [`v1.3.1`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.3.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.3.0...1.3.1) #### 🚀 Enhancements

Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @renovate (#88)

cloudposse/terraform-aws-s3-bucket

##### [`v3.1.1`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.0...3.1.1) ##### 🐛 Bug Fixes

Revert change to Transfer Acceleration from #178 @Nuru (#180)

##### what - Revert change to Transfer Acceleration from [#178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) ##### why - Transfer Acceleration is not available in every region, and the change in [#178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported

***

#### 🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @renovate (#88)

cloudposse/terraform-aws-s3-bucket

Revert change to Transfer Acceleration from #178 @Nuru (#180)

***

### [`v1.3.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.3.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.2.0...1.3.0) #### 🚀 Enhancements

Enhance lifecycle object with optionals, limit length of bucket name @Nuru (#87)

#### what - Limit length of auto-generated bucket name to match AWS-imposed limit - Enhance `lifecycle_configuration_rules` to be fully defined with optional members #### why - Avoid situation where module fails because auto-generated bucket name is too long - Make it easier to build a list of rules #### references - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - [https://github.com/cloudposse/terraform-aws-s3-bucket/issues/167](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/167)

### [`v1.2.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.2.0): Support new AWS S3 defaults (ACL prohibited) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.1.0...1.2.0) #### 🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.0 @renovate (#85)

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudposse/s3-bucket/aws](https://registry.terraform.io/modules/cloudposse/s3-bucket/aws) ([source](https://togithub.com/cloudposse/terraform-aws-s3-bucket)) | module | minor | `3.0.0` -> `3.1.0` | *** ##### Release Notes

cloudposse/terraform-aws-s3-bucket

##### [`v3.1.0`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.0.0...3.1.0)

Make compatible with new S3 defaults. Add user permissions boundary. @Nuru (#178)

##### what - Make compatible with new S3 defaults by setting S3 Object Ownership before setting ACL and disabling ACL if Ownership is "BucketOwnerEnforced" - Add optional permissions boundary input for IAM user created by this module - Create `aws_s3_bucket_accelerate_configuration` and `aws_s3_bucket_versioning` resources even when the feature is disabled, to enable drift detection ##### why - S3 buckets with ACLs were failing to be provisioned because the ACL was set before the bucket ownership was changed - Requested feature - See [#171](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/171) ##### references - Closes [#174](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/174) - Supersedes and closes [#175](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/175) - Supersedes and closes [#176](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/176)

Always include `aws_s3_bucket_versioning` resource @mviamari (#172)

##### what - Always create an `aws_s3_bucket_versioning` resource to track changes made to bucket versioning configuration ##### why - When there is no `aws_s3_bucket_versioning`, the expectation is that the bucket versioning is disabled/suspend for the bucket. If bucket versioning is turned on outside of terraform (e.g. through the console), the change is not detected by terraform unless the `aws_s3_bucket_versioning` resource exists. ##### references - Closes #171

Add support for permission boundaries on replication IAM role @mchristopher (#170)

##### what - Adds support for assigning [permission boundaries](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) to the replication IAM role ##### why - Our AWS environment enforces permission boundaries on all IAM roles to follow AWS best practices with security. ##### references - [AWS IAM Access Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html)

##### 🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#164)

##### what This is an auto-generated PR that updates the README.md and docs ##### why To have most recent changes of README.md and doc from origin templates

***

### [`v1.1.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.1.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.0.0...1.1.0)

Adding "object_lock_configuration" variable @ramses999 (#84)

#### what Adding "object_lock_configuration" variable which is used in module "cloudposse/s3-bucket/aws" #### why Must be able to use the Object Lock option for S3 in this module #### references https://github.com/cloudposse/terraform-aws-s3-bucket/blob/6837ed7b2f2460043d6be3981f16ed90563fd12a/main.tf#L5

### [`v1.0.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.0.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/0.28.3...1.0.0) #### Important Notes - Terraform version 1.3.0 and Terraform AWS version 4.9.0 or later are required - The new `bucket_key_enabled` flag defaults to `false` for backward compatibility. At one point we recommend setting it to true for significant savings on KMS usage, but since bucket keys are only reused within a user session, it is not clear if it provides any savings at all. See [AWS docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-key.html) for more information. - The new `lifecycle_configuration_rules` input replaces the now deprecated individual inputs for individual settings of a single lifecycle rule. See the [terraform-aws-s3-bucket documentation](https://togithub.com/cloudposse/terraform-aws-s3-bucket/blob/6837ed7b2f2460043d6be3981f16ed90563fd12a/variables.tf#L122-L154) for details on how to specify lifecycles using `lifecycle_configuration_rules`. This mechanism is much more flexible and closely follows the Terraform `aws_s3_bucket_lifecycle_configuration` resource. - The new `source_policy_documents` input replaces the now deprecated `policy` input to match changes to the `aws_iam_policy_document` resource - You can now select default values for (non-deprecated) inputs by setting them to `null` - With Terraform 1.3 the manual interventions documented for upgrading to this module's versions 0.27.0 and 0.28.0 are no longer needed. You can safely upgrade from any earlier version to this one (although we always recommend leaving `force_destroy` at its default value of `false`, and if you have it set to `true` but want extra safety against the S3 bucket being destroyed, set it to `false` ***before*** upgrading). - The `force_destroy_enabled` flag introduced in v0.27.0 has been removed - In version 0.28.0, old lifecycle rule variables were deprecated and the new `lifecycle_configuration_rules` input was introduced. In that version, you would continue to get the old default lifecycle rule even if you supplied new rules via `lifecycle_configuration_rules`. Now, the default behavior is to ignore all the deprecated lifecycle inputs when the `lifecycle_configuration_rules` input is not empty, unless you explicitly set `lifecycle_rule_enabled` to true. *** ##### Enhancements

Automate upgrade using `moved` blocks @Nuru (#81)

#### what - Automate the upgrade process from v0.26.0 or earlier by using `moved` block functionality introduced in Terraform 1.3.0 - Add `nullable = false` for module input variables which have a default value and where null is not a sensible/handled value for the variable. #### why - Safely upgrade without loss of data or manual intervention - Allow users to select default values by setting inputs to `null`, closes [#63](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/issues/63)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 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 Mend Renovate. View repository job log here.

cloudposse / terraform-aws-cloudfront-cdn

Update Terraform cloudposse/s3-log-storage/aws to v1 (release/v0) #107

Release Notes

Configuration

Edited/Blocked Notification