This is the Food52 fork the the thumbor AWS plugin, which lets thumbor use AWS as a source of originals and a sink for results.

Our Changes

1. Don't hash the results path. By default, when thumbor saves the result to S3 for an image path like:

/asdlkfjasdfa=/100x100/test.png

it hashes the entire key. This interferes with our redirecting from S3 to thumbor. So we save the result in S3 using a cleartext version of the path.

2. We explicitly set mime type when saving to S3.

3. We explicitly set the cache-control headers.

Branches, Tags

In production we currently deploy master.

Original Readme Follows

• thumbor_aws.loaders.s3_loader
• thumbor_aws.result_storages.s3_storage
• thumbor_aws.storages.s3_storage

Additional Configuration values used:

# the Amazon Web Services access key to use
AWS_ACCESS_KEY = ""
# the Amazon Web Services secret of the used access key
AWS_SECRET_KEY = ""



# configuration settings specific for the s3_loader

# list of allowed buckets for the s3_loader
S3_ALLOWED_BUCKETS = []



# configuration settings specific for the storages

# put data into S3 using the Server Side Encryption functionality to
# encrypt data at rest in S3
# https://aws.amazon.com/about-aws/whats-new/2011/10/04/amazon-s3-announces-server-side-encryption-support/
S3_STORAGE_SSE = True or False (Default: False)

# put data into S3 with Reduced Redundancy
# https://aws.amazon.com/about-aws/whats-new/2010/05/19/announcing-amazon-s3-reduced-redundancy-storage/
S3_STORAGE_RRS = True or False (Default: False)

# Use Role-based connection
# http://docs.aws.amazon.com/IAM/latest/UserGuide/roles-assume-role.html
AWS_ROLE_BASED_CONNECTION = True or False (Default: False)


#Optional config value to enable the HTTP loader
#This would allow you to load watermarks in over your images dynamically through a URI
#E.g. 
#http://your-thumbor.com/unsafe/filters:watermark(http://example.com/watermark.png,0,0,50)/s3_bucket/photo.jpg
AWS_ENABLE_HTTP_LOADER = True or False (Default: False)