You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/changelog/r2/2025-03-06-r2-bucket-locks.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ date: 2025-03-06T10:00:00Z
8
8
9
9
You can now use [bucket locks](/r2/buckets/bucket-locks/) to set retention policies on your [R2 buckets](/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.
10
10
11
-
Locks allow you to:
11
+
Locks give you a few ways to ensure your objects are retained (not deleted or overwritten). You can:
12
12
13
-
- Lock objects for a specific duration. For example, 90 days.
14
-
-Retain objects until a certain date. For example, until January 1, 2030.
15
-
-Keep objects locked indefinitely.
13
+
- Lock objects for a specific duration, for example 90 days.
14
+
-Lock objects until a certain date, for example January 1, 2030.
15
+
-Lock objects indefinitely, until the lock is explicitly removed.
16
16
17
17
Buckets can have up to 1,000 [bucket lock rules](/r2/buckets/). Each rule specifies which objects it covers (via prefix) and how long those objects must remain retained.
0 commit comments