| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
Working with Amazon S3 Import Manifests
These options are used with Amazon S3 import jobs.
Topics
Handling Gzip Files
When importing Gzip compressed files you can set the
setContentEncodingForGzFiles option to
yes. This adds the Content-Encoding header, in addition to the
Content-Type header, when the Gzip compressed files are uploaded. The
Content-Encoding header helps most browsers render these files correctly.
setContentEncodingForGzFiles: yes
Additionally, the extensions, .gz and .gzip are
ignored when setting the Content-Type header if the file has been compressed
with Gzip.
For example, if setContentEncodingForGzFiles is set to "yes", the
compressed file compressed using Gzip text1.html.gz, is uploaded with the
following HTTP headers:
Content-Encoding: gzip
Content-Type: text/html
The gzip compressed file, text2.html, is uploaded
with the following HTTP headers:
Content-Encoding: gzip
Content-Type: text/html
The non-compressed file, text3.html, is uploaded with the following
HTTP headers:
Content-Type: text/html
Note
When setContentEncodingForGzFiles is set to
yes, only files that are gzip compressed will contain a
Content-Encoding header. We look at the first few bytes of all imported
files to see if they are compressed using Gzip. If so, they get the Content-Encoding header
regardless of the file extension.
The gzip compressed file, text.gzip, is uploaded with the following
HTTP headers using the defaultContentType specified in
the manifest file:
Content-Encoding: gzip
Content-Type: binary/octet-stream
Setting ACL on Imported Amazon S3 Objects
When importing data to Amazon S3, the permissions on the imported objects is
set as private. You can specify the acl manifest option to
specify the access control list (ACL) on the imported objects. The following
manifest option sets the ACL value on the uploaded objects to
public-read.
acl: public-read
