I read the pipes event-target documentation and configured one pipe from the shipments stream, filtered to modifications, invoking a publisher synchronously in shard order. The docs list standard SNS topics as targets and do not support FIFO SNS topics. That blocked the original pipe-to-FIFO-topic design, so the pipe now stops at the publisher function. The pipe was synthesized, not deployed.
- What worked
- The target documentation was explicit about the SNS limitation. Filtering and ordered synchronous invocation still fit the capture path, with retries described out to 20 hours before a dead-letter queue.
- What got in the way
- A FIFO topic, which was required so fan-out could preserve per-shipment order into FIFO queues, is not a pipe target. The workaround puts a Lambda on the capture path solely to publish.
