aws_s3_bucket lifecycle_rule should support filter

[kimor79]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS recently announced support for filtering objects by size in an S3 bucket lifecycle policy. It would be nice if this was also available in the aws_s3_bucket resource.

Example from AWS documentation:

<LifecycleConfiguration>
    <Rule>
        <Filter>
            <ObjectSizeGreaterThan>500</ObjectSizeGreaterThan>   
        </Filter>
        <Status>Enabled</Status>
        transition/expiration actions.
    </Rule>
</LifecycleConfiguration>

New or Affected Resource(s)

• aws_s3_bucket

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

resource "aws_s3_bucket" "my-bucket" {
  ...

  lifecycle_rule {
    id = "archive"
    enabled = true

    transition {
      days = 90
      storage_class = "GLACIER"
    }

    filter {
      object_size_greater_than = 128000
    }
  }
}

References

• https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-lifecycle-storage-cost-savings/
• https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html#intro-lifecycle-rules-filter

[visit1985]

Maybe we can add the new versions action parameters for noncurrent_version_transition and noncurrent_version_expiration from the same announcement in the same effort.

Potential Terraform Configuration

resource "aws_s3_bucket" "my-bucket" {
  ...

  lifecycle_rule {
    id = "archive"
    enabled = true

    noncurrent_version_transition {
      storage_class = "STANDARD_IA"
      versions = 4
    }

    noncurrent_version_expiration {
      versions = 4
    }
  }
}

References

• https://docs.aws.amazon.com/AmazonS3/latest/API/API_NoncurrentVersionTransition.html#AmazonS3-Type-NoncurrentVersionTransition-NewerNoncurrentVersions
• https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html

[dhermes]

I was just about to file an issue requesting NewerNoncurrentVersions support as well, thanks @visit1985

[pda]

I see object_size_greater_than and object_size_less_than filters are supported in the aws_s3_bucket_lifecycle_configuration resource type provided by v4.x of hashicorp/terraform-provider-aws.

Landed in d8640c1 / #22579 / v4.0.0 (11 Feb 2022):

resource/aws_s3_bucket: The lifecycle_rule argument has been deprecated and is now read-only. Use the aws_s3_bucket_lifecycle_configuration resource instead. (#22581)

Documentation:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_lifecycle_configuration#specifying-a-filter-based-on-object-size

I imagine there's no intention to backport it onto the v3.x aws_s3_bucket resource, so maybe this issue should close?

A bit more context:

• Discussion around changes made to the aws_s3_bucket resource in AWS Provider version 4.0 #23106
• https://www.hashicorp.com/blog/terraform-aws-provider-4-0-refactors-s3-bucket-resource
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.