Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ParameterDescriptionDefault Value
access-key

Access key

-
secret-keyPassword-
urlURL for S3-
bucketName of the bucket in the archive system for filing.-

defaultRetentionInDays

Retention time in days.

Note: Objects under retention can still be deleted by administrators having direct access to the S3 storage.

To transmit no retention time, set the value 0.

For objects with a scheduled retention time, this has priority over any times specified here.

If the profile is used for a repository used as rendition repository, the parameter is ignored for the storage of renditions as they cannot be under retention. However, if binary content files are stored in the same repository beside the renditions, the defaultRetentionInDays value is NOT ignored for the storage of binary content files.

0

region
(as of 2022 Autumn)

Specifies the location of the data center where to create new buckets.
If not specified, it is automatically determined via the S3 method GetBucketLocation.

-

objectLock
(as of 2022 Autumn)

Boolean value that decides if the archive-internal retention (objectLock) is required (true) or optional (false) for the corresponding bucket.

If true is set:

  • Binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention can only be stored in buckets with activated ObjectLocking.
  • Buckets automatically created by the ARCHIVE service will have activated objectLock.

If false is set:

  • For binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention stored in buckets with activated  ObjectLocking, an archive-internal retention will be set.
  • For binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention stored in buckets with deactivated ObjectLocking, no archive-internal retention will be set. Thus, binary content files can only be protected from manipulation via yuuvis® Momentum endpoints but not from manipulation by direct storage access.
  • Buckets automatically created by the ARCHIVE service will have deactivated objectLock.

In both cases: For objects without retention specified via secondary object type (SOT) system:rmDestructionRetention, no archive-internal retention is set. 

true
pathTemplate

Optional: This parameter can be used to store objects in specific directories (paths) within a bucket.

If the profile is used for a rendition repository, use only the contentStreamId as a placeholder in the specified path. Do not include a DATE reference to avoid path changes for each rendition update (Instead of a rendition update, a new rendition would be created and the previous rendition would have to be deleted.)

-
retentionMode

Optional parameter to select a retention mode for S3 Object Lock.

Available values:

  • COMPLIANCE - objects under retention cannot be modified/deleted even by a storage administrator.
  • GOVERNANCE - storage users with specific permissions can modify/delete objects under retention.
COMPLIANCE

Parameters for NetApp Archive Profiles

...

ParameterDescriptionDefault Value
access-key

Access key

-
secret-keyPassword-
urlURL for S3-
bucketName of the bucket in the archive system for filing.-

defaultRetentionInDays

Retention time in days.

Note: Objects under retention can still be deleted by administrators having direct access to the S3 storage.

To transmit no retention time, set the value 0.

For objects with a scheduled retention time, this has priority over any times specified here.

If the profile is used for a repository used as rendition repository, the parameter is ignored for the storage of renditions as they cannot be under retention. However, if binary content files are stored in the same repository beside the renditions, the defaultRetentionInDays value is NOT ignored for the storage of binary content files.

0

region

Specifies the location of the data center where to create new buckets.
If not specified, it is automatically determined via the S3 method GetBucketLocation.

-

objectLock

Boolean value that decides if the archive-internal retention (objectLock) is required (true) or optional (false) for the corresponding bucket.

If true is set:

  • Binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention can only be stored in buckets with activated ObjectLocking.
  • Buckets automatically created by the ARCHIVE service will have activated objectLock.

If false is set:

  • For binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention stored in buckets with activated  ObjectLocking, an archive-internal retention will be set.
  • For binary content files under retention specified via secondary object type (SOT) system:rmDestructionRetention stored in buckets with deactivated ObjectLocking, no archive-internal retention will be set. Thus, binary content files can only be protected from manipulation via yuuvis® Momentum endpoints but not from manipulation by direct storage access.
  • Buckets automatically created by the ARCHIVE service will have deactivated objectLock.

In both cases: For objects without retention specified via secondary object type (SOT) system:rmDestructionRetention, no archive-internal retention is set. 

true
pathTemplate

Optional: This parameter can be used to store objects in specific directories (paths) within a bucket.

If the profile is used for a rendition repository, use only the contentStreamId as a placeholder in the specified path. Do not include a DATE reference to avoid path changes for each rendition update (Instead of a rendition update, a new rendition would be created and the previous rendition would have to be deleted.)

-
retentionMode

Optional parameter to select a retention mode for S3 Object Lock.

Available values:

  • COMPLIANCE - objects under retention cannot be modified/deleted even by a storage administrator.
  • GOVERNANCE - storage users with specific permissions can modify/delete objects under retention.
COMPLIANCE

Parameters for Azure Blob Storage Profiles

...