Skip to content

Releases: cloudposse/terraform-aws-s3-bucket

v0.34.0

08 Apr 17:49
35484d3
Compare
Choose a tag to compare
Optional Object lock configuration added @maximmi (#84)

what

  • Optional object_lock_configuration added

why

  • to be able to configure S3 object locking

references

v0.33.0

04 Apr 05:06
999fe3e
Compare
Choose a tag to compare
Rebase #49: Policy to allow only ssl uploads @pperzyna (#82)

This is a rebase of PR #49

what

  • Adds enable flag to allow only ssl/https bucket uploads.
  • Includes logic to merge other policies enabled by the user such as the string policy passed in via the policy variable and the other encryption policy. This prevents overriding the user defined policy (mentioned in issue #11) as long as the sid values are distinct.

why

  • Provides compliance with AWS Config rule s3-bucket-ssl-requests-only.
  • Fixes an outstanding issues which prevents users from specifying their own policy string and enabling userful policies pre-defined within the module.

references

v0.32.0

25 Mar 17:30
183f4ed
Compare
Choose a tag to compare
Add `bucket_name` variable @aknysh (#80)

what

  • Add bucket_name variable

why

  • Allow users to override the name of the created bucket instead of generating it from the context
  • Useful in situations when a bucket needs to have a name without namespace, environment, name in it

references

In order for the S3 bucket to proxy (not just basic CNAME) through Cloudflare, 
the bucket name has to match the domain.  
That way we can have the bucket completely behind Cloudflare and not exposed to the world, 
provided we added the policy to restrict access from Cloudflare's IP.

v0.31.0

22 Feb 09:43
90d5dcd
Compare
Choose a tag to compare
S3deeparchive support @bcoddens (#78)

Support transition to the deep archive storage class
We need this for our business.

v0.30.3

09 Feb 00:09
6fc0987
Compare
Choose a tag to compare

🤖 Automatic Updates

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#75)

what

  • update context.tf to v0.24.1
  • minimum required Terraform version bumped to 0.13.0
  • readme updated, Bridgecrew compliance badges added

why

  • It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
  • we have dropped support for Terraform 0.12
  • To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.30.2

09 Feb 00:00
0cbf446
Compare
Choose a tag to compare

🚀 Enhancements

Cross-account replication fix @bmwosz (#69)

what

  • Add missing replication policy permissions

why

  • Without this permission cross-account replication is not possible

references

  • #68
  • closes #68

v0.30.1

05 Feb 03:15
8fa399e
Compare
Choose a tag to compare

🤖 Automatic Updates

Update context.tf @cloudpossebot (#72)

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.30.0

04 Feb 15:12
35887b4
Compare
Choose a tag to compare
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#74)

what

  • update context.tf to v0.23.0
  • minimum required Terraform version bumped to 0.13.0
  • readme updated, Bridgecrew compliance badges added

why

  • It allows for setting the letter case of tag names and labels
  • we have dropped support for Terraform 0.12
  • To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.29.1

03 Feb 04:07
38e9bef
Compare
Choose a tag to compare

🤖 Automatic Updates

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

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

v0.29.0

30 Jan 14:29
cdb0697
Compare
Choose a tag to compare
Bc compliance @maximmi (#70)

what

  • BridgeCrew compliance checks fix
  • readme updated
  • default behaviour changed: S3 bucket MFA delete enabled by default
  • default behaviour changed: S3 Bucket Versioning enabled by default
  • default behaviour changed: Encryption of the S3 bucket enabled by default

why

  • To be able to position our modules as standards compliant
  • stay in sync with code
  • To comply BridgeCrew check

references