R2 - Set retention polices for your R2 bucket with bucket locks

You can now use bucket locks to set retention policies on your R2 buckets (or specific prefixes within your buckets) for a specified period — or indefinitely. This can help ensure compliance by protecting important data from accidental or malicious deletion. Locks give you a few ways to ensure your objects are retained (not deleted or overwritten). You can: Lock objects for a specific duration, for example 90 days. Lock objects until a certain date, for example January 1, 2030. Lock objects indefinitely, until the lock is explicitly removed. Buckets can have up to 1,000 bucket lock rules . Each rule specifies which objects it covers (via prefix) and how long those objects must remain retained. Here are a couple of examples showing how you can configure bucket lock rules using Wrangler : Ensure all objects in a bucket are retained for at least 180 days npx wrangler r2 bucket lock add --name 180-days-all --retention-days 180 Prevent deletion or overwriting of all logs indefinitely (via prefix) npx wrangler r2 bucket lock add --name indefinite-logs --prefix logs/ --retention-indefinite For more information on bucket locks and how to set retention policies for objects in your R2 buckets, refer to our documentation .

R2 - Set retention polices for your R2 bucket with bucket locks

Source

You might also wanna read

Mythos-class AI models to retain user prompts and outputs for 30 days under new safety policy

Mythos-class AI models to retain user prompts and outputs for 30 days under new safety policy

Keeper: A Cryptographic Secret Management Tool for Go Applications

The 4-Year Journey to Creating a Python Lock File Specification

Deployment-Time Memorization in Foundation-Model Agents: Privacy-Utility Tradeoffs in Persistent Memory Systems

The Global Namespace Risk: Universal Bucket Hijacking Technique for Cloud Data Exfiltration

AWS Implements Solution to S3 Bucketsquatting Security Issue After Decade-Long Problem

Comments