到SQS的S3通知是否有可能失败? [英] Is it possible for S3 notifications to SQS to fail?

问题描述

我已经设置了一个S3存储桶，以便为每个PUT和POST操作发布消息.使用CLI将文件上传到该存储桶.它确实可以正常工作，但是在顺序推送的4个文件中，只有一个触发了一条消息.我不确定这是否一直发生，但现在正在持续发生.请注意，当我手动上传文件时，它不会不会发生(即，每个文件我总是收到一条消息).

I have setup an S3 bucket to publish messages for each PUT and POST actions. Files get uploaded to that bucket using CLI. It does work fine but out of 4 files pushed sequentially, only one triggers a message. I am not sure that this has always happened but it is happening consistently now. Note that it does not happen when I upload file manually (i.e. I always get a message per file).

我确保没有下游系统处理消息(作为确认，我仍然看到在第一个文件之后触发的原始​​消息).

I have made sure that there is no downstream system processing the messages (as a confirmation, I still see the original message triggered after the first file).

是否有任何理由相信此AWS功能不可靠?由于这不太可能，这里可能是什么问题?

Is there any reason to believe that this AWS feature is not reliable? Since this is unlikely, what could be the problem here?

推荐答案

正如迈克尔在评论中所建议的那样，问题在于存储桶仅收听了s3:ObjectCreated:Put.发生的是，除第一个文件外，所有其他文件都是使用multipart上载的，这不会触发任何消息创建.

As suggested by Michael in the comment, the problem was that the bucket only listened to s3:ObjectCreated:Put. What was happening is that all other files but the first one were uploaded using multipart which was not triggering any message creation.

我修改了存储段以触发s3:ObjectCreated:*上的消息，现在它可以按预期运行.

I modified the bucket to trigger messages on s3:ObjectCreated:* and it now works as expected.

这篇关于到SQS的S3通知是否有可能失败?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！