Cloudformation-coverage-roadmap: AWS::S3::Bucket-Rule-ExpiredObjectDeleteMarker

[cccassidy]

1. Title

AWS::S3::Bucket-Rule-ExpiredObjectDeleteMarker

2. Scope of request

Add ExpiredObjectDeleteMarker option to S3 lifecycle policy specifications.

3. Expected behavior

Enable/Disable remove of expired object delete markers

Resources:
  S3Bucket:
    Type: AWS::S3::Bucket
    Properties:
      LifecycleConfiguration:
        Rules:
          - Id: DeleteMarker
            Prefix: "/"
            Status: Enabled
            ExpiredObjectDeleteMarker: true

5. Helpful Links to speed up research and evaluation

https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html#lifecycle-config-conceptual-ex7

6. Category (required) - Will help with tagging and be easier to find by other users to +1

Storage (S3, EFS, Backup...)

[rectalogic]

@TheDanBlanco Is there any way to get this onto the roadmap?

[TheDanBlanco]

we prioritize items mostly based on +1's. you can almost always accurately track which items we're looking at putting on our roadmap by filtering for +1's.

[benkehoe]

To clarify, by +1s you mean positive reaction emojis on the issue?

[TheDanBlanco]

yep!

[benkehoe]

It's usually better etiquette to use reactions (the "😀" button on a comment) than to have lots of individual people clutter up the comments (and notifications) with "+1" comments. And when you put 👍 on an issue, it's easier to see the support for an issue right up front!

[TheDanBlanco]

ben's right! please only use emoji reactions to the initial post as that's how we determine which items to work on. we'll be deleting any comments that just say +1 as they only serve to clutter the discussion. thank you!

[dflanzer-s1]

@TheDanBlanco do you know, if you're maintaining a bucket via cloudformation, and you go in and set the ExpiredObjectDeleteMarker checkbox in the console, will that cause stack drift? Or since it's not CF-able, it will avoid interference?

[cccassidy]

@dflanzer-s1 What I've seen is subsequent updates to the S3 bucket through CloudFormation will remove any manual lifecycle policies you enter from the console.

[LaikaN57]

@dflanzer-s1 Just confirmed, drift detection will detect a drift.

[markatthrive]

+1 from me; this is a real pain point for us currently.

[jonathanwcrane]

+1

[LaikaN57]

@markatthrive @jonathanwcrane Can you please react +1 to the issue as well if you have not done so. They only use that to determine issue sort order. Comments are ignored.

[Ricapar]

This is a pretty critical setting on S3 especially if you're using it as a backend for Athena or other systems that are querying the bucket.

I have a lifecycle policy that expires old versions to keep the bucket clean, but I'm left with an abundance of delete-markers that slow down s3:List* performance significantly.

For now I'm left with no choice than to drift the stack by modifying the lifecycle rule.

It's been nearly a year since this was submitted and this item is No. 2 on the most +1'd issues on the tracker. Is this going to happen?

[efenderbosch]

Now 15 months old and the highest +1'd issue. Any update on roadmap?

[LYLeon]

+1

[MikeKroell]

+1

[benbridts]

@MikeKroell @LYLeon @jonathanwcrane @markatthrive

If you react with the 👍 button to the original issue, (the first comment, click on the smiley face if you're the first reacting), your votes can be used to sort issues and determine priorities.

A comment will send a notification to everyone (participants and watchers), but cannot be easily counted as a vote for an issue. Thus It's generally better to vote than to comment with "+1". To keep up to date, you can also add yourself as a watcher.

[markatthrive]

@LaikaN57 @benbridts Yes, I already upvoted that when I posted my comment. 194 upvotes and we're still waiting.

[jonathanwcrane]

we prioritize items mostly based on +1's. you can almost always accurately track which items we're looking at putting on our roadmap by filtering for +1's.

I just sorted all the issues in this repo by +1s and this issue is in first place. All 5 of the top 5 are from 2019. Seems like AWS makes progress on requested features about as quickly as container ships can currently navigate the Suez Canal.

[craigataws]

We are actively working on releasing (moved item to "Coming Soon"). While I can't provide an exact date for official release, it is targeted for Q2.

[tstibbs]

@craigataws will that change in cloudformation come with a corresponding change in the high-level constructs in CDK? Or will there then have to be a separate ticket logged against CDK?

[richardhboyd]

@tstibbs There will most likely need to be a change to the high-level CDK Construct to support a new CloudFormation resource.

[urda]

Is this still on track for a Q2 release?

[craigataws]

@urda, yes

[icalvete]

+1

[rohits-spec]

Launched on 5/14. Resolving the issue.

[joebernard]

For anyone curious the new docs are here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-bucket-lifecycleconfig-rule.html#cfn-s3-bucket-rule-expiredobjectdeletemarker

[LaikaN57]

Thank you to the community for upvoting this and holding strong. And thank you to AWS for getting this across the line! Good work all.