No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

Looks like there is a Terraform issue open for it: <https://github.com/hashicorp/terraform-provider-aws/issues/22561>

You can use s3control in the AWS classic provider: <https://www.pulumi.com/registry/packages/aws/api-docs/s3control/bucketlifecycleconfiguration/>

Doesn't look like the cloud control API has it yet, I can't see it in AWS Native.

<@U012UJTT55M> this doesn’t seem to have it either:

<https://www.pulumi.com/registry/packages/aws/api-docs/s3control/bucketlifecycleconfiguration/#bucketlifecycleconfigurationruleexpiration>

That one doesn’t even have a way to control the current version vs non-current version at all.

If you want versioning, just set the `versioning` property to `true` on the bucket. Then you can use `lifecycleRules` to control the lifecycle.
<https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucket/#versioning_nodejs>
<https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucket/#lifecyclerules_nodejs>

<@U012UJTT55M> I don’t think this resolves the original question. We have versioning enabled on the bucket (using Pulumi) and lifecycle rules (using Pulumi), but it looks like this specific capability (of being able to control the expiration date of non-current objects *and* set a minimum number of non-current versions to keep) is available in either Terraform or Pulumi.

I can express this lifecycle policy in the AWS console (or API), just not in IAC at the moment.

This is my default setup:
```lifecycleRules: [{
        enabled: true,
        noncurrentVersionExpiration: {
          days: 364,
        },
        noncurrentVersionTransitions: [
        {
          days: 29,
          storageClass: "GLACIER"
        }
      ]
      }```

Ah, I missed that a minimum number of versions was required. Sorry.

All good :slightly_smiling_face: We have a similar policy to yours:

```			&amp;s3.BucketLifecycleRuleArgs{
				Enabled: pulumi.Bool(true),
				Id:      pulumi.String("audit"),
				Prefix:  pulumi.String(fmt.Sprintf("%s/", tenant.TENANT_AUDIT_LOGS_PREFIX)),
				NoncurrentVersionExpiration: &amp;s3.BucketLifecycleRuleNoncurrentVersionExpirationArgs{
					Days: <http://pulumi.Int|pulumi.Int>(1),
				},
			},```

I just want to say “delete all non-current versions after a day, but keep 1 non-current version around”.

I’ll wait for the Terraform PR to be merged and will then open a ticket on `pulumi-aws` to get it there - appreciate the notes!

If it's important in the short term, it should be feasible to use the AWS SDK to update the lifecycle rules after the Pulumi program finishes..

I can handle it for now, so it’s OK.

The main issue with that approach is that I now need to have something else besides Pulumi (or use the automation API), which I’m trying to avoid. But it’s a good suggestion overall, so thank you.