Considerations when using Object Lock

Content Platform Tenant Management Help

File Size
4269 KB
Part Number

When using Object Lock, it is important to consider the following factors to ensure that your data is properly protected and managed.

  • If you don’t configure retention mode for a new namespace, HCP automatically selects HCP Enterprise mode with a Deletion Allowed retention policy as the default setting.
  • After you upgrade to HCP release 9.6, the namespaces that existed earlier will have their new Retention Type setting set to HCP retention.
  • If you upgrade to HCP release 9.6, you cannot modify existing namespaces from an earlier version to use S3 Object Lock.
  • Do not replicate a namespace in HCP release 9.6 that uses S3 Object Lock retention type to an older HCP release that doesn’t support S3 Object Lock. Doing so may pause the replication link.
  • You can set the Retention Type as S3 Object Lock when you create a new namespace and apply S3 Object retention mode and retention period default values to that namespace. However, you cannot change the retention type of existing namespaces to S3 Object Lock.
  • When configuring namespaces that use S3 Object Lock, you cannot use existing retention related namespace configuration options that conflict with S3 Object Lock. For example, retention period values that Amazon S3 does not support, initial unspecified, event-based retention, and retention classes are not allowed.
  • HCP supports S3 APIs for configuring and retrieving retention modes, retention periods, and legal hold.
  • The namespace permission structure will be expanded to enforce the S3 permissions required to execute these new retention related APIs.
  • Retention periods in HCP do not offer the same level of precision as milliseconds, as observed in Amazon S3 Object Lock. However, HCP ensures data preservation with a resolution down to the level of seconds.