Skip to main content

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 "cmybucketname]" 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?

Hi there @asago - Thanks for the question! That error appears when it cannot find new data associated with the Zap. However, that doesn’t mean that your data isn’t there in the bucket. Our Zapbook about Amazon S3 is outlined here: https://zapier.com/apps/amazon-s3/integrations#triggers-and-actions - It seems the only two Triggers we have at the moment are “New Bucket” and then “New or Updated File” - Could you confirm which of the two triggers you’re trying when you’re seeing that error?

Thanks!


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.


Hi Liz,

I am having the same issue. I’m trying to connect a Box folder to an S3 bucket. The trigger is meant to fire when a file is uploaded to a folder within Box and should upload the file to an S3 bucket. When it comes to choosing a bucket, I get this general error after several seconds in the right sidebar that says:

“We’re having trouble loading 'Bucket Name' data

Uh oh, something is not quite right! This might be a temporary problem though, so you may want to try that again or contact support if this persists!”

None of the S3 buckets, whether they are in the North California region or not, are showing.

Since the API that finds bucket names fails, I would appreciate it if I could enter the name of the bucket manually instead.

Also, I believe that the “Bucket Name” field should probably be required. It is currently optional.


Of course, the test of the integration fails since the bucket name is empty.


Hi @Johnh! It’s possible this may be the same bug, but I suggest reaching out to our Support team so that they might confirm. They can look at your specific configuration to troubleshoot and/or add you to a bug report if needed. They can be reached here!


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.


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.


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!


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. 


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. 


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.


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.


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.


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.


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.


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


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.


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

 

Any updates?


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.


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. 


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!


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! 


I am having the same problem.


Same issue as OP using the New or Updated file… works fine until the test section… 

  1. bucket was empty press test. Response - the bucket “Bucket-Name” does not exist.
  2. upload a new file to the bucket, press test. Response - the bucket “Bucket-Name” does not exist.

Tested permissions with script and it is fine for the access keys given, also tried AmazonS3FullAccess policy to see if it was part of the read only settings… but still did nothing…. useless. 


Hi @wdenny3885 ,

I see you are working with Caleb in Support on this issue and have stumbled upon a bug with the S3 integration. You have been added to the bug report which means you will be notified when there is an update. 

I see Caleb suggested a possible workaround some folks have found is to move the S3 bucket to the "N California" region which may be helpful as this bug is worked out. 

I know that’s not the answer you were hoping for, but please let us know if you have any additional questions!

 

 


Any resolution on this? Having the same issue with the Zap.


Reply