13 ms·

Link? The eTag of an object is still the MD5 AFAIK.

• xxpor 6y ago
  The request signature (assuming version 4) is SHA256, the object eTag is MD5.
• eadan 6y ago
  Yes, S3 uses the content-md5 header to verify data integrity for puts. https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjec...
• rob-olmos 6y ago
  For the ETag, yes and no that it's an MD5 of the object depending on encryption and multipart upload: https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonResponseHeaders.html https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRe... For the object upload, AWSv4 request signature uses SHA256 on the payload/object, but I don't know if S3 also computes & compares the digest or just uses the x-amz-content-sha256 header value.
  • rob-olmos 6y ago
    AWS support via Twitter said that the SHA256 digest of the payload is calculated and compared for S3 when using AWSv4 signature requests.