This post demonstrates how you can create a bunch of resized images right after uploading an image to S3. The solution requires no servers, is scalable and can be automatically deployed within minutes.
The solution makes use of two S3 buckets:
- The bucket that contains the original images. Users upload images to this bucket. This bucket is suffixed with
-originalin the following example.
- The bucket that contains the resized images. The bucket is suffixed with
-resizedin the following example.
When you upload an image to the
-original bucket a Lambda function is executed. The Lambda function downloads the image from S3, creates multiple resized versions and uploads them to the
-resized S3 bucket. As of now three resized copies are created for every upload to
150xfixed width, height is scaled as needed
50x50scale image best into box
x150fixed height, width is scaled as needed
The following figure demonstrates the image resizing process in detail.
You can find out how ImageMagick resize works or read on to deploy the solution.
==WARNING: This example assumes that you have installed and configured the AWS Command Line Interface==
Clone this repository …
or download and extract the zipped repository.
Create an S3 bucket for your Lambda code in the US East (N. Virginia,
us-east-1) region and upload the
lambda.zip file (replace
$LambdaS3Bucket with a S3 bucket name e.g.
==WARNING: This bucket has nothing to do with the resizing of images. It contains the zipped source code of the Lambda function.==
Create a CloudFormation stack (replace
$ImageS3Bucket with a name for your image bucket e. g.
$LambdaS3Bucket with your Lambda code S3 bucket name).
Wait until the stack is created (retry if you get
CREATE_IN_PROGRESS this can take a few minutes).
You can now upload your first image to the
-original S3 bucket (you can also use the web based Management Console if you prefer).
You will see the resized images in the
-resized bucket (you can also use the web based Management Console if you prefer).
As you can see, for every size configuration a new “directory” was created.
From this point you can think about how to enable your users to upload files into the
-original S3 bucket if your use cases requires user generated content. To allow uploads from your users you should think about a way to protect your
-original bucket with IAM permissions. You could use the Security Token Service to achieve this.
You should use CloudFront in combination with the
-resized bucket to serve the resized images to your end users. This will decrease the latency by pushing your content to one of the edge locations of the CloudFront CDN network.
Remove all files in the
Delete the CloudFormation stack.
Delete Lambda code S3 bucket (replace
If you want to make changes to the code you need to create a new lambda code file (
lambda.zip) and upload the new zip to S3. You can adjust the
config.json file to adjust the size configurations.
AWS Lambda can respond to S3 events like a new file was uploaded. The Lambda function will download the original image from S3 to create new resized images. The resized images are then upload to S3 again. The Lambda solution in scalable and does not require any operational work.
This blog post has been translated into German: Serverless die Größe von Bildern anpassen.