Amazon S3 and Amazon EBS Log File Fields
The following table describes the fields in an Amazon S3 or Amazon EBS log file.
|DateTime||The date and time when we processed a file, for example, |
|File||The name of the file in the root directory of your storage device, for example,
|Status||Specifies either an AWS Import/Export status or one of the standard Amazon S3 REST web server
HTTP status codes, for example, |
|Code||Specifies either an AWS Import/Export code, such as |
Specifies where AWS Import/Export loads the file in Amazon S3. The key includes the bucket
name and any prefix settings set in the manifest file, for example,
The checksum of the object stored in Amazon S3 identified by
Objects imported into Amazon S3 use the public Amazon S3 API actions. Smaller objects are uploaded by Import/Export using PUT Object, and larger objects are uploaded using Multipart Upload. Objects created by PUT Object have ETags that are an MD5 digest of their object data. However, objects created by Multipart Upload have ETags that are not MD5 digests. Therefore, ETags from S3 might not match your local MD5 sums.
With AWS Import/Export import jobs, we compute the MD5 sum before uploading each part, and provide it as input to UploadPart. The MD5 sum of the entire file is then written to one of our internal logs. Once the upload is complete, all data on the disk is automatically re-read to calculate MD5 sums to compare against the MD5 sums of the imported objects. If, for any reason, the software reads an MD5 sum that doesn’t match, the entire workflow will the section called “Failed Jobs”.
For more information on how ETags and MD5 sums are computed in Amazon S3, see Common Response Headers in the Amazon Simple Storage Service API Reference.
|Bytes||The number of bytes stored in Amazon S3 for the object identified by
|Content-Type||The value of the |
|ETag||The ETag value of the object in Amazon S3.|