Get started using Resizor

Back to documentation

1. Make sure you have a Amazon Web Services (AWS) account

This is needed because Resizor uses Amazon's S3 service to store the files it processes for you. By using S3 for storage your Resizor files are stored safely in Amazon's infrastructure and you maintain full access to them.

Sign up for a Amazon Web Servies account here if you don't already have one.

2. Create a S3 bucket and grant Resizor access to it.

Login to your AWS account a click the S3 tab. Click the ”Create bucket button”. Enter a name for the bucket, for example ”my-app-resizor-assets”. Select a region, right now (during the beta) it is encouraged to use the Ireland region as Resizor is hosted in that region to ensure maximum performance between Resizor and your bucket endpoint, however Resizor will work with buckets in other regions. Click the ”Create button”.

The bucket is now created and it is time to grant Resizor permission to interact with the bucket. Right-click the bucket in the list and select ”Properties”. Under the ”Permissions” tab click the ”Add more permissions” button, type ”” into the grantee field, check all the checkboxes for that row and click the ”Save” button.

Now login in to your account on and select that you want to ”add a S3 bucket”. Enter the name of the bucket exactly as you entered it when you created it on AWS, select the region and click the ”Save” button.

3. Create a CloudFront distribution

This step is optional but is highly recomended if you are using Resizor for a production site as it ensures that the resized images served with Resizor will be served super fast to your visitors via Amazon's Content Delivery Network.

Return your AWS account and click the ”CloudFront” tab. Click the ”Create distribution” button, select ”Custom Origin”, enter your Resizor CDN origin host (available on the account screen on Resizor) as ”Origin DNS name” and click ”Continue”. On the next screen the defaults are good, you can just click ”Continue” and ”Create Distribution” on the last screen. The new distribution should now show in the distributions list it might take a minute or so for it to get the ”Enabled” status.

What you just did enables you to request resizing of images through CloudFront. If CloudFront doesn't have the resizied image cached it will request it from Resizor automatically and if CloudFront already have the resized image it will send it without requesting it from Resizor. With this setup you get a fast and geo-aware way of serving your resized images.

CloudFront requires you to use the CDN-compatible version of the asset resize request.

4. Setup your app to use Resizor

How this is done depends on what language and framework you use. However you will need to know your Resizor API-key and CDN-host (if you did the CloudFront step) in most cases. The API-key is found on the account screen when logged in on Resizor and the CDN-host is the domain name / CNAME for the CloudFront distribution which is visible if you select the distribution in the AWS interface.

If you are using Ruby checkout the resizor gem and example app. More examples in other langauges are coming soon and if you have any questions don't hesitate to get in contact with us.