<p>If I recall, they should get created on S3 and also cached locally.</p>

<p>But if I try to load <a href="https://s3-eu-west-1.amazonaws.com/rallyagency/_200x200_crop_center-center_75/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg?mtime=20141217123237" rel="nofollow">https://s3-eu-west-1.amazonaws.com/rallyagency/_200x200_crop_center-center_75/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg?mtime=20141217123237</a> directly, I'm getting an "Access Denied" error, so it looks like you've got some S3 permission issues.</p>

CC BY-SA 3.0
2014-12-23T17:07:52.637Z
Yes exactly. I've got a policy set for public read access and I have a key set up for full access that Craft uses. Presumably the issue is with the key, not the public policy?
Russ Back
CC BY-SA 3.0
2014-12-23T21:17:12.390Z
Thanks, Brad. Looks like my access key worked but wasn't up-to-date with the latest IAM setup in AWS. Now sorted.
Russ Back
CC BY-SA 3.0
2015-11-05T19:13:17.237Z
Brad, what if we are using Cloudfront in conjunction with s3? In that case I don't think we would want craft caching the images, right?
David A McInnis
CC BY-SA 3.0
2014-12-23T16:52:52.097Z
2014-12-23T16:52:52.097Z
Brad Bell
<p>I've just set up an S3 bucket and have a transform in my template. Should these transformed images be saved on S3? It doesn't look like they are, however my template is pulling out an S3 URL:</p>

<pre><code>&lt;img src="{{ asset.getUrl(resize) }}" width="{{ asset.getWidth(resize) }}" height="{{ asset.getHeight(resize) }}" alt="A photograph of {{ entry.title }}" class="grayscale grayscale-fade wp-post-image ral-mugshot"&gt;
</code></pre>

<p>When using a base image at <a href="http://s3-eu-west-1.amazonaws.com/rallyagency/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg" rel="nofollow">http://s3-eu-west-1.amazonaws.com/rallyagency/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg</a>, my template outputs this:</p>

<pre><code>&lt;img src="http://s3-eu-west-1.amazonaws.com/rallyagency/_200x200_crop_center-center_75/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg?mtime=20141217123237" width="200" height="200" alt="A photograph of Ali Meredith" class="grayscale grayscale-fade wp-post-image ral-mugshot"&gt;
</code></pre>

<p>Note the addition of the directory <strong>_200x200_crop_center-center_75</strong> in the path - that doesn't exist on the S3 bucket.</p>

<assets><image-transforms><s3>
Asset transforms saved on S3 storage
# Asset transforms saved on S3 storage

(Asked by: username_0 on 2014-12-23)

I've just set up an S3 bucket and have a transform in my template. Should these transformed images be saved on S3? It doesn't look like they are, however my template is pulling out an S3 URL:


When using a base image at http://s3-eu-west-1.amazonaws.com/rallyagency/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg, my template outputs this:


Note the addition of the directory _200x200_crop_center-center_75 in the path - that doesn't exist on the S3 bucket.

**Tags:** assets, image-transforms, s3

---

## 1 answers

### Answer by username_1 on 2014-12-23. Score: 1 | Accepted answer

If I recall, they should get created on S3 and also cached locally.

But if I try to load <https://s3-eu-west-1.amazonaws.com/rallyagency/_200x200_crop_center-center_75/princess-leia-princess-leia-walking-in-new-york-is-just-plain-awesome.jpeg?mtime=20141217123237> directly, I'm getting an "Access Denied" error, so it looks like you've got some S3 permission issues.

> **Comments:**
> **username_0**: Yes exactly. I've got a policy set for public read access and I have a key set up for full access that Craft uses. Presumably the issue is with the key, not the public policy?  
> **username_0**: Thanks, Brad. Looks like my access key worked but wasn't up-to-date with the latest IAM setup in AWS. Now sorted.  
> **username_2**: Brad, what if we are using Cloudfront in conjunction with s3? In that case I don't think we would want craft caching the images, right?  

---

