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?
+8
Hi there
Thanks!
Same issue as OP using the New or Updated file… works fine until the test section…
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.
+8
Hi
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.
+8
In the meantime, hoping the workaround mentioned above may be an option for you!
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.
Same issue with me.
The IAM user has full S3 permissions. When I customize the file, it queries S3 and finds the bucket name. When I test the trigger I get “A file could not be found” and then underneath that it tells me the bucket I select does not exist.
It both exists and there is data in the bucket.
+12
Hi,
Any update on this issue? Having the exact same problem. Moving S3 bucket to a random region because this bug is not solved is not an option.
+8
I am having the same problem.
Hi, trying to add form data to an S3 bucket but I get this error: We’re having trouble loading 'Bucket Name' data”
Is this a bug?
Thanks
John
+8
Hi
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?
Hello,
I have the same issue as mentioned above… Any news of a fix ?
Thanks!
Jean
+8
Hi
Thanks for your answer - unfortunately this didn’t help.
Do you have any visibility on a due date for this fix ?
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?
+11
Hi
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.
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.
+11
Hey
It’s too bad that the suggestion didn’t help, but I’m glad you found something that works for you :)
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.
+11
Hi
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.
+11
Hey
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
