Bug 1797784
| Summary: | [rfe][rgw] Support S3 Object-lock | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Heðin <hmoller> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
| Severity: | medium | Docs Contact: | Ranjini M N <rmandyam> |
| Priority: | high | ||
| Version: | 4.1 | CC: | cbodley, ceph-eng-bugs, gsitlani, kbader, kdreyer, lithomas, mbenjamin, rmandyam, sweil, tchandra, uboppana, vereddy, vumrao |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | 5.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.1.0-486.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.Users can now use object lock to implement WORM-like functionality in S3 object storage
The S3 Object lock is the key mechanism supporting write-once-read-many (WORM) functionality in S3 Object storage.
With this release, {storage-product} 5 supports Amazon Web Services (AWS) S3 Object lock data management API and the users can use Object lock concepts like retention period, legal hold, and bucket configuration to implement WORM-like functionality as part of the custom workflow overriding data deletion permissions.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-30 08:23:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1890843 | ||
| Bug Blocks: | 1959686 | ||
|
Description
Heðin
2020-02-03 21:00:56 UTC
1890843 blocks this BZ and is targeted beyond 5.0, so I'm re-targeting this one as well. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 5.0 bug fix and enhancement), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3294 |