Commit 557deef
authored
### Motivation
Currently, the SQS subscription from the S3 bucket events uses
`filterPolicy`, which only filters based on message attributes.
However, S3 event notifications do **not include the object key as a
message attribute** — the key is only present in the JSON message body.
As a result, all messages are being filtered out (see
`NumberOfNotificationsFilteredOut-NoMessageAttributes` metrics),
preventing the SQS queue from receiving any messages.
To solve this, we need to filter messages based on the object key inside
the message body rather than expecting message attributes.
<!-- TODO: Say why you made your changes. -->
### Modifications
- use `filterPolicyWithMessageBody` instead of `filterPolicy`.
<!-- TODO: Say what changes you made. -->
<!-- TODO: Attach screenshots if you changed the UI. -->
### Verification
<img width="1400" height="319" alt="image"
src="https://github.com/user-attachments/assets/47491e2a-21d5-4da7-a066-fdf91a876af4"
/>
<!-- TODO: Say how you tested your changes. -->
1 parent 0e8df7c commit 557deef
1 file changed
+10
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
| 2 | + | |
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
36 | | - | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
37 | 45 | | |
38 | 46 | | |
39 | 47 | | |
| |||
0 commit comments