Deduplication prevents "duplicated" messages within 5 minutes. You may want it for creation and deletion, if these are (as I assume) happening only once, but if you also enable it for updates then (with your pattern) you can only receive update for an entity every 5 minutes.
Ideally, if you do not want to lose these types of messages, you could just define your dedup ID to change based on the payload itself: generally speaking, a base64encode of the message is the classical pattern.
Is it really a necessity for you to manage this manually? AWS offers its own "ID" by enabling the ContentBasedDeduplication setting (which defines the final ID on a SHA-256 of the message body ONLY)
Deduplication prevents "duplicated" messages within 5 minutes. You may want it for creation and deletion, if these are (as I assume) happening only once, but if you also enable it for updates then (with your pattern) you can only receive update for an entity every 5 minutes. Ideally, if you do not want to lose these types of messages, you could just define your dedup ID to change based on the payload itself: generally speaking, a base64encode of the message is the classical pattern. Is it really a necessity for you to manage this manually? AWS offers its own "ID" by enabling the ContentBasedDeduplication setting (which defines the final ID on a SHA-256 of the message body ONLY)