# CORS issue with AWS S3 urls

**URL:** <https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888>\
**Category:** Ask us anything\
**Created:** [April 22, 2025, 6:34pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888 "2025-04-22T18:34:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikm3103](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erikm3103](https://community.weweb.io/u/erikm3103)\
**Post date:** [April 22, 2025, 6:34pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/1 "2025-04-22T18:34:47Z")

</div>

Convinced that something is not working correctly. I have checked CORS and allowed the necessary in the S3 bucket in AWS.

I can confirm it’s accessible publicy. However, when I try to download it in Weweb, I get an error. I still think it’s cors related, but can’t figure out how or why.

Any ideas? See the error here:

 ![Screenshot 2025-04-22 at 20.33.02](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/073eb664f72274dbcee0852d66cf5e00c842aedc.png)

Here you can see it’s accessible:

 ![Screenshot 2025-04-22 at 20.30.32](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/0f666ff3532b00829085b0510a3bc1c971e64e5f.png)

Any tips is welcome!

---

<div class="post-metadata">

**Author:** ![erikm3103](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erikm3103](https://community.weweb.io/u/erikm3103)\
**Post date:** [April 22, 2025, 6:38pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/2 "2025-04-22T18:38:44Z")

</div>

Here is an example url for reference: \* [https://smil-foto.s3.eu-north-1.amazonaws.com/files/22298fa7-acde-4fca-828f-3c2172c4897c.jpeg](https://smil-foto.s3.eu-north-1.amazonaws.com/files/22298fa7-acde-4fca-828f-3c2172c4897c.jpeg)

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [April 22, 2025, 9:22pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/3 "2025-04-22T21:22:30Z")

</div>

Hi @erikm3103 👋

Mmm… I’m not sure why the error message is mentioning WeWeb’s CDN since you are hosting the image on your own S3 bucket in AWS.

Could you add a `Log` action inside the loop but before the “Download file from URL” action to log the name of URL being fetched? This could help us confirm the input is correct.

Can you also show us what’s inside the “Download file from URL” action?

---

<div class="post-metadata">

**Author:** ![erikm3103](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erikm3103](https://community.weweb.io/u/erikm3103)\
**Post date:** [April 23, 2025, 7:08am UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/4 "2025-04-23T07:08:28Z")

</div>

Super strange, I just moved the log into the loop, ran the test and it worked now!

**Did not change anything from closing my computer yesterday.**

 ![Screenshot 2025-04-23 at 09.07.16](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/984bbb54021cb6fdaceef408ce0e203950cad90a.jpeg)

Perhaps some type of cache?

 ![Screenshot 2025-04-23 at 09.07.17](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/a/ae6e296bfbf1dbc83b0f2b7495424f8010ecc5aa.png)

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [April 23, 2025, 5:13pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/5 "2025-04-23T17:13:06Z")

</div>

Ha! No idea. Glad it worked out. Don’t hesitate to reach out if you run into the issue again

---

<div class="post-metadata">

**Author:** ![erikm3103](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erikm3103](https://community.weweb.io/u/erikm3103)\
**Post date:** [April 27, 2025, 1:33pm UTC](https://community.weweb.io/t/cors-issue-with-aws-s3-urls/17888/6 "2025-04-27T13:33:24Z")

</div>

Hi @Joyce ,  
It happened again now, here is the info you asked for.

 ![Screenshot 2025-04-27 at 15.31.09](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/f196425a2bb45572fda9d01ae4a17cab11789f9b.png)  
 ![Screenshot 2025-04-27 at 15.31.39](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/7/791c9d429f3ece212c89d61fe13fd35d1630b683.png)
