Skip to main content

Hello,

I am trying create a Zap that accesses a file that is stored in an S3 bucket.

I’ve accomplished this with the file accessible to the public using an http url, but need to lock it down more. As far as I know, Zapier is authenticated using my provided id/key so it should be no problem to access this file with Zapier.

I’m using step “Amazon S3 > New or Updated File” which gets the filename I need properly.  I then am using step “Amazon S3 > Get Object” to try to get this file.  As I said, if I provide a public http URL to this step, it works fine, but that is not sufficiently secure.  

When testing the step, “Data In” shows the correct s3url (in my case, i am attempting to use s3://bucket-name/folder/filename), but I get the error “Failed to find an object in Amazon S3. The app returned an error with no further details.”

I’ve checked multiple times and the principle associated with the ID/key is explicitly allowed “s3:GetObject” so I don’t quite understand what the issue might be. Would be nice to see what the actual error is somehow...

Can someone help me understand how I can troubleshoot this further?

Thanks!

Hi ​@jrefano 

Help us have more info by posting these screenshots:

  • how your Zap steps are outlined
  • how your Zap steps are configured in EDIT mode with the field mappings visible in the CONFIGURE tab
  • any encountered errors testing Zap steps

If I switch the s3url from s3://bucket-name/filename to https://fileurl with the file permissions set to public, it works. 

 

I am just trying to determine if the S3 Get Object is actually authenticating with the keys provided in the first “Get new or updated file” step as it seems like that is not happening.


Hi ​@jrefano,

 

If you're having trouble accessing an S3 file using the s3:// URL format in Zapier, it's likely due to authentication issues. Ensure your AWS Access Key and Secret Key are correct and the associated IAM user has s3:GetObject permission. Check that the bucket policy allows access, the region is correctly set, and the Zap is appropriately configured. If public access works but private does not, it's likely a permissions issue. Review Zapier's task or error details, and if the problem persists, reaching out to Zapier Support is a good next step.

If you have any further questions or need more assistance, feel free to ask.