About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Failed to fetch a new or updated file from Amazon S3 Error while retrieving: Bucket "xxxx"

  • 24 February 2023
  • 1 reply
  • 300 views
cadoad

Hi guys, 

 

I am trying to create a new Zap to fetch new files from a S3 Bucket. Everything works fine until the test trigger.

 

I got the following error message :

   

I have read a few posts on this community about the quite same issue.

 

Any workaround please ?

 

Thank you all 💪

icon

Best answer by SamB 24 February 2023, 12:42

View original

1 reply

SamB
Rank
Userlevel 7
Badge +11

Hey @cadoad, welcome to the Community!

Ah yes, it sounds like you’re running into the bug mentioned on this related topic: 

I’ve added you to the list of users being affected by that so we can notify you by email as soon as it’s resolved. We’ll post any news on that front in the related topic so please do subscribe to it for future updates on that!

There’s a workaround mentioned on that post about moving the S3 bucket to the "N California" region which should allow it to be seen by the Zap.

If you’ve already tried that and it didn’t work, I remember an instance from when I worked on the Support team where a customer changed the policy/permissions to make the condition keys less specific and got it working. If you give that a try and it does the trick please let us know! 🙂

Reply


Terms & Conditions