Operations on objects
Suggest changes
PDFs
This section describes how the StorageGRID system implements S3 REST API operations for objects.
The following conditions apply to all object operations:
-
StorageGRID consistency controls are supported by all operations on objects, with the exception of the following:
-
GET Object ACL
-
OPTIONS / -
PUT Object legal hold
-
PUT Object retention
-
SELECT Object content
-
-
Conflicting client requests, such as two clients writing to the same key, are resolved on a "latest-wins" basis. The timing for the "latest-wins"evaluation is based on when the StorageGRID system completes a given request, and not on when S3 clients begin an operation.
-
All objects in a StorageGRID bucket are owned by the bucket owner, including objects created by an anonymous user, or by another account.
-
Data objects ingested to the StorageGRID system through Swift cannot be accessed through S3.
The following table describes how StorageGRID implements S3 REST API object operations.
| Operation | Implementation |
|---|---|
DELETE Object |
Multi-Factor Authentication (MFA) and the response header When processing a DELETE Object request, StorageGRID attempts to immediately remove all copies of the object from all stored locations. If successful, StorageGRID returns a response to the client immediately. If all copies cannot be removed within 30 seconds (for example, because a location is temporarily unavailable), StorageGRID queues the copies for removal and then indicates success to the client. Versioning To remove a specific version, the requestor must be the bucket owner and use the
Note: In certain cases, multiple delete markers might exist for an object. |
DELETE Multiple Objects |
Multi-Factor Authentication (MFA) and the response header Multiple objects can be deleted in the same request message. |
DELETE Object tagging |
Uses the Versioning If the |
GET Object |
|
GET Object ACL |
If the necessary access credentials are provided for the account, the operation returns a positive response and the ID, DisplayName, and Permission of the object owner, indicating that the owner has full access to the object. |
GET Object legal hold |
|
GET Object retention |
|
GET Object tagging |
Uses the Versioning If the |
HEAD Object |
|
POST Object restore |
|
PUT Object |
|
PUT Object - Copy |
|
PUT Object legal hold |
|
PUT Object retention |
|
PUT Object tagging |
Uses the Object tag limits You can add tags to new objects when you upload them, or you can add them to existing objects. Both StorageGRID and Amazon S3 support up to 10 tags for each object. Tags associated with an object must have unique tag keys. A tag key can be up to 128 Unicode characters in length and tag values can be up to 256 Unicode characters in length. Key and values are case sensitive. Tag updates and ingest behavior When you use PUT Object tagging to update an object's tags, StorageGRID does not re-ingest the object. This means that the option for Ingest Behavior specified in the matching ILM rule is not used. Any changes to object placement that are triggered by the update are made when ILM is re-evaluated by normal background ILM processes. This means that if the ILM rule uses the Strict option for ingest behavior, no action is taken if the required object placements cannot be made (for example, because a newly required location is unavailable). The updated object retains its current placement until the required placement is possible. Resolving conflicts Conflicting client requests, such as two clients writing to the same key, are resolved on a "latest-wins" basis. The timing for the "latest-wins"evaluation is based on when the StorageGRID system completes a given request, and not on when S3 clients begin an operation. Versioning If the |