<p>Check what region you created bucket versus what you have configured locally.  I typically use us-east-1 (N. Virginia) but I didn't notice AWS console had defaulted to us-east-2 (Ohio).</p>

CC BY-SA 4.0
2024-12-06T16:38:48.567Z
2024-12-06T16:38:48.567Z
Alex Aguilar
<p>I have just set up my first S3/CloudFront service to handle assets and it all seems to be connected right, but when I upload an asset into the volume that is stored on S3, I get this odd error in CraftCMS which I haven't been able to find many resources about:</p>
<p><a href="https://i.sstatic.net/0aEmV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/0aEmV.png" alt="Screenshot of &quot;Unable to check if  exists&quot; error" /></a></p>
<p>This doesn't appear to be a permissions/policy error as this was a separate error I had in the process of putting this together. I have tried to upload different images in the hope the one I was trying was corrupt, but it appears to be happening with all.</p>

CC BY-SA 4.0
2024-05-28T09:24:45.253Z
Hi Jay, did you resolve this issue? I've hit a wall with the same thing.
Mark
<assets><craft4><s3><aws>
Amazon S3/Cloudfront bucket providing "Unable to check if <img> exists" error when uploading an asset
# Amazon S3/Cloudfront bucket providing "Unable to check if <img> exists" error when uploading an asset

(Asked by: username_0 on 2024-01-08)

I have just set up my first S3/CloudFront service to handle assets and it all seems to be connected right, but when I upload an asset into the volume that is stored on S3, I get this odd error in CraftCMS which I haven't been able to find many resources about:

[![Screenshot of ](https://i.sstatic.net/0aEmV.png)](https://i.sstatic.net/0aEmV.png)

This doesn't appear to be a permissions/policy error as this was a separate error I had in the process of putting this together. I have tried to upload different images in the hope the one I was trying was corrupt, but it appears to be happening with all.

**Tags:** assets, craft4, s3, aws
> **Comments:**
> **username_1**: Hi Jay, did you resolve this issue? I've hit a wall with the same thing.  

---

## 1 answers

### Answer by username_2 on 2024-12-06. Score: 0

Check what region you created bucket versus what you have configured locally. I typically use us-east-1 (N. Virginia) but I didn't notice AWS console had defaulted to us-east-2 (Ohio).


---

