Initiate Multipart Upload

The x-amz-storage-class request header is supported with the following enumerated values:

• STANDARD

  (Default) Specifies a dual-commit ingest operation. As soon as an object is ingested, a second copy of that object is created and distributed to a different Storage Node. When the object is matched by an ILM rule in the active policy, StorageGRID determines if the initial, dual-commit copies satisfy the placement instructions in the rule. If they do not, the object is added to the ILM evaluation queue. When the object is re-evaluated, new object copies might need to be made in different locations, and the initial dual-commit copies might need to be deleted.

• REDUCED_REDUNDANCY

  Specifies a single-commit ingest operation. Specify REDUCED_REDUNDANCY only if you need to limit redundant storage at the time of ingest and only if you are willing to risk the loss of object data. For example, you might lose data if the single copy was initially stored on a Storage Node that failed before ILM evaluation could occur.

  Specifying REDUCED_REDUNDANCY only affects how many copies are created when an object is first ingested. It does not affect how many copies of the object are made when it is evaluated by the active ILM policy. Using REDUCED_REDUNDANCY does not result in data being stored at lower levels of redundancy in the StorageGRID system.

  Note: You cannot use the REDUCED_REDUNDANCY option if you are ingesting an object into an S3 compliant bucket. This is to ensure that compliance requirements are satisfied (two copies of each object exist) before the object is evaluated by the active ILM policy. See the instructions for administering StorageGRID.

The following request headers are supported:

• Content-Type
• x-amz-meta-, followed by a name-value pair containing user-defined metadata
  When specifying the name-value pair for user-defined metadata, use this general format:

  x-amz-meta-name: value

  If you want to use the User Defined Creation Time option as the Reference Time for an ILM rule, you must use creation-time as the name of the metadata that records when the object was created. For example:

  x-amz-meta-creation-time: 1443399726

  The value for creation-time is evaluated as seconds since January 1, 1970.

  Note: Adding creation-time as user-defined metadata is not supported if you are adding an object to a S3 compliant bucket. An error will be returned.
• x-amz-server-side-encryption (Previously, you could specify the x-amz-server-side-encryption header for each of the upload parts; starting with the StorageGRID 11.2 release, this implementation is no longer supported.)

The following request headers are not supported and return XNotImplemented:

• x-amz-server-side-encryption-customer-algorithm
• x-amz-server-side-encryption-customer-key
• x-amz-server-side-encryption-customer-key-MD5
• x-amz-website-redirect-location

Versioning

Multipart upload consists of separate operations for initiating the upload, listing uploads, uploading parts, assembling the uploaded parts, and completing the upload. When the Complete Multipart Upload operation is performed, that is the point when objects are created (and versioned if applicable).