v0.40.1 S3 updates
🤖 Automatic Updates
Update Terraform cloudposse/s3-log-storage/aws to v1.3.1 (release/v0) @renovate (#134)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-log-storage/aws (source) | module | minor | 1.1.0 -> 1.3.1 |
Release Notes
cloudposse/terraform-aws-s3-log-storage
v1.3.1
🚀 Enhancements
Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @renovate (#88)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.0 -> 3.1.1 |
Release Notes
cloudposse/terraform-aws-s3-bucket
v3.1.1
🐛 Bug Fixes
Revert change to Transfer Acceleration from #​178 @​Nuru (#​180)
what
- Revert change to Transfer Acceleration from #178
why
- Transfer Acceleration is not available in every region, and the change in #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)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.0 -> 3.1.1 |
Release Notes
cloudposse/terraform-aws-s3-bucket
v3.1.1
🐛 Bug Fixes
Revert change to Transfer Acceleration from #​178 @​Nuru (#​180)
what
- Revert change to Transfer Acceleration from #178
why
- Transfer Acceleration is not available in every region, and the change in #178 (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported
v1.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
v1.2.0
: Support new AWS S3 defaults (ACL prohibited)
🤖 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 (source) | module | minor | 3.0.0 -> 3.1.0 |
Release Notes
cloudposse/terraform-aws-s3-bucket
v3.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
andaws_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
references
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 theaws_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 to the replication IAM role
why
- Our AWS environment enforces permission boundaries on all IAM roles to follow AWS best practices with security.
references
🤖 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