Getting Started

​ ​Welcome

Blitline Job

Job Response

Job Options

Functions

Polling and Postbacks

Gotchas

Development Recommendations

Service Limits

Examples List

List of Available Functions

Output Options

S3 Destination

IAM Users

S3 Signed Url

Azure Destination

FTP Destination

Other Service Signed Urls

CDN

Advanced

Metadata

Colorspace

Color Extraction

Static IPs

Signed Jobs

Formats

Pipelines

Image Optimization

Smart Image

PDF

Fonts

Subimage

Special (Non-Image) Processing

AWS Rekognition/Facial Recognition

Apache Tika

Vector Processing

Animated GIFs

Screenshots of Websites

IM Scripts

Video Keyframes

Zipping

​ ​Trancoding Video Presets

​ ​Video Transcoding

S3 Signed Url

Updated a month ago ​by Blitline Support

NEW! SIGNED URLS

AWS offers the ability to sign a url which means you can give us ONLY a url, and we are allowed to upload to that specific location in your bucket. http://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html.

The benefit of this is that you do not need to give Blitline any permissions to your buckets. The signed url contains all the information necessary.IF you use signed urls you also do not need to set your Canonical ID on Blitline.com, because we do not need it.

Important : You must be able to generate a signed_url on your own. We (Blitline) cannot generate it for you. Most modern AWS SDKs allow for creation of these signed_urls

To use these signed urls with Blitline, the “signed_url” sits within an s3_destination like this:

{
      "s3_destination" : {
        "signed_url" : "https://s3.amazonaws.com/images.blitline/everything_is_awesome.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJM928347239487232%2F20150225%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20150225T014313Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=fa389a132b45a0d79ef59f8421bdbae4ef8339f5046e2af7444454bca319cd65",
        "headers" : {
          "x-amx-acl" : "public-read"
        }
    }
}
Remember: If you signed a url with headers, you must include those same headers in the s3_destination




How did we do?