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 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

Amazon S3 Bucket error: A File could not be found. Bucket "[mybucketname]" does not exist.

A
Userlevel 1

Trying to connect S3 to Google drive.  I am able to enter the access and secret to my bucket and the bucket is found (and it has files within) but Zapier is reporting (after successfully connecting) that “bucket does not exists” and no files found.  Specifically:

Find Data (error)

  • A File could not be found.

    Bucket "[mybucketname]" does not exist.

I’ve tried everything I can think of here… all I want to do is move everything from S3 to Google drive.  Is this possible?

icon

Best answer by Liz_Roberts 23 July 2020, 20:56

View original

38 replies

ken.a
Userlevel 7
Badge +6

Hi there @Branden,

I’m so sorry to the inconvenience this bug has caused you. I have added you as another affected member to the open bug report. While we can’t provide a timeframe on when this bug will get fixed, we will keep you in the loop via email once it is.

Thank you for your understanding.

Branden

I guess I will join in on this issue. I am going to assume this is not going to be fixed anytime soon LOL.

 

Would love to have this working! 

christina.d
Userlevel 7
Badge +9

Ah, appreciate you letting me know. I’m sorry to hear that didn’t work for you. 

While I don’t have any other workarounds to share at the moment, we’ll keep the thread informed if one comes up.

Thanks again for reaching out!

andymmc

Hey there @andymmc - no updates at the moment, I’m sorry to say!

I’m curious is moving the S3 bucket to the "N California" region feasible for your setup? It was mentioned earlier in the read but definitely recognize not an option for everyone.

In the meantime, I did add you as an affected user and we’ll be sure to update the thread with any news.

The bucket was already located in us-west-1 N. California. 

christina.d
Userlevel 7
Badge +9

Hey there @andymmc - no updates at the moment, I’m sorry to say!

I’m curious is moving the S3 bucket to the "N California" region feasible for your setup? It was mentioned earlier in the read but definitely recognize not an option for everyone.

In the meantime, I did add you as an affected user and we’ll be sure to update the thread with any news.

andymmc

I’m having the same issue. Two years later.

 

Any updates?

JammerS
Userlevel 6
Badge +3

Hi @truss 

I apologize, but we don’t have any update yet regarding with this bug to share. Hence, I added you to the existing bug report for you to get updated via email once available. We appreciate your patience.

jammer․solijon
A

Have there been any developments on this?  I’m having the issue as well.

JammerS
Userlevel 6
Badge +3

Hi @rockc 

 

We don’t have any updates yet regarding this bug. I added you to the existing bug report for you to get updated via email once available. We appreciate your patience.

jammer․solijon
R

Have recently encountered this issue. Was wondering if there’s any updates on plans for fixing this - I see that the initial thread creation was July 2020, almost 2 years now.

christina.d
Userlevel 7
Badge +9

Thanks for reaching out and sharing your thoughts with us, @fabphoto. I definitely understand your disappointment and want to be as helpful as possible.

I did a bit of digging and can see you had a chance to chat with my teammate, Scott in support. He was able to add you to the existing bug report. He also had this workaround he recommended:

 

In the meantime, I have seen users get around this bug in a few ways. Would you be able to move the bucket region to N.California on AWS? If that does not work, would you be able to create a new bucket in that region to test?

 

I know it’s been mentioned earlier in the thread but it could be worth a shot. In the meantime, since you’ve been added to that report we’ll be sure to keep you and this thread updated with any news just as soon as we have it. Thank you once again for taking the time to reach out.

F

This is very disheartening to read this thread. I just upgraded our clients Zapier to premium to gain access to the Amazon S3 Premium App and now it appears it doesn’t work. I have contacted support about it, but it seems many others have tried many things and nothing seems to work. Hoping I can find a resolution to this.

D

I have tried the S3 trigger with every possible combination of events, permissions, regions, etc. with absolutely no success. I don’t see any way to get it working, whatsoever.

Even making a brand new bucket, keeping the permissions completely public, and triggering events on any new file added to it does not work. 

If anyone reading this thread has been able to get the s3 trigger to work for them at all, please let me know what you did in order to do so.

nicksimard
Userlevel 7
Badge +11

Hey @david123,

I agree with you that this is certainly worth fixing but with limited resources we do have to make decisions on what to address first.

If the integration didn’t work at all, for anyone whatsoever, then of course we would not claim to have such an integration and call it premium. The fact is that this bug affects a relatively small percentage of users. There are hundreds of live and functional Zaps, where the users have managed to connect the account and successfully test the trigger. 

Again, I’m really sorry that you (and the others in this thread) are not able to get it working. I really am. It may not feel like a minor bug to you since it’s a total blocker, but it is the case that most people who are using the Amazon S3 integration are doing so successfully (which I understand is no consolation to you).

It doesn’t look like you’ve reached out to our Support team yet about this particular issue. I certainly can’t promise that they’ll be able to resolve this for you, but they have access to more resources than we do here in Community and may have some workarounds that haven’t been mentioned in this thread. 

D

Sure, i totally understand how you have deprioritized this and dont think its worth fixing now. That’s fine, but you CANT claim to have a premium S3 integration on your site then and not fix it for more than 10 months with no timeline for a fix. That’s borderline fraud.

To be perfectly clear - your S3 integration does not work, at all, in any capacity right now. I have tried every single method triggering it and there is no way to get it to function. 

This is not a minor bug that only affects some specific edge cases. The integration is NOT FUNCTIONAL.

So either fix this, or remove the integration from your site and stop claiming you have it. 

nicksimard
Userlevel 7
Badge +11

Hi @david123!

I understand how frustrating this issue is, and I apologize for the inconvenience of it all. 

We have a multi-faceted prioritization system in place, with teams looking at all of the various requests that we have. Part of it is no doubt whether the integration is a premium one, but there are other factors as well (including how many users it impacts).

As much as I wish I could give you an ETA for when this will be resolved, that’s not something I can provide.

I get that this isn’t necessarily a satisfying answer, but it's the best I can offer right now. You'll be notified this bug has been resolved, and hopefully that's sooner than later!

D

No updates still?

 

The s3 New or Updated File Trigger doesn’t work at all and it’s a premium integration, one that we are paying for and need badly. I’ve tried making the bucket region northern california, ive tried making the bucket completely public, ive tried making the IAM permissions completely open. 

Nothing is working, and i continue to get the error message that the bucket does not exist when i try to test it.

nicksimard
Userlevel 7
Badge +11

Hey @beyondgravity!

It’s too bad that the suggestion didn’t help, but I’m glad you found something that works for you :) 

B
Userlevel 1

I ended up changing the policy to make it less specific for the Keys and got it working. Since I am the only one with access to the zapier account and the bucket.

 

I guess they mean giving more access to the AWS service account that it should need, like for example, giving it full write/read access.

I already tried it, but it didn’t worked out for me.

Anyway, thanks for the help, i found another complete different solution to solve my problem.

nicksimard
Userlevel 7
Badge +11

Hi @jean-stonly and @beyondgravity!

While I’m not able to provide an ETA for this to be fixed, I can pass along what one user said to our Support team that got things working for them.

They said:

I ended up changing the policy to make it less specific for the Keys and got it working. Since I am the only one with access to the zapier account and the bucket.

Full disclosure: I’m not totally familiar with what they’re suggesting, but if this makes sense to you and is something you’re able to do, it may be worth trying.

B
Userlevel 1

Hi,

We have the same issue : we try to make a copy of all our S3 bucket to google drive.

S3 Bucket is in Europe west region, and as the company is based in France, we cannot move the bucket to California or anything like that.

Any solution?

Any date about fixing this bug?

J

Thanks for your answer - unfortunately this didn’t help.

Do you have any visibility on a due date for this fix ?

Liz_Roberts
Userlevel 7
Badge +8

Hi @jean-stonly - sorry you are running into this! I have added you as an impacted user, which means you will receive updates via email. I see that one user has had success by "changing the policy to make it less specific for the Keys.” I’m not sure if that is helpful in your case but worth sharing!

J

Hello,

I have the same issue as mentioned above… Any news of a fix ?

Thanks!

Jean

 

 

E

Same problem. Since this hasn’t been fixed for such a long time, does anyone know of an alternative to Zapier for this use case?

Reply


Terms & Conditions