Processing requests arrive in SQS and must be passed to Step Functions.
Avoid building a polling Lambda and retain retry handling for failed messages.
Which automation approach is most appropriate?
Use EventBridge Pipes with SQS as the source and a workflow as the target, with DLQ and visibility settings designed explicitly.
Detailed explanation
Returning audit records does not guarantee the original request was processed.
Returning audit records does not guarantee the original request was processed.
S3 lifecycle rules do not process SQS messages.
S3 lifecycle rules do not process SQS messages.
Pipes provides managed polling, filtering, transformation, and target invocation.
Pipes provides managed polling, filtering, transformation, and target invocation.
Scaling, visibility timeouts, and error handling become custom operational code.
Scaling, visibility timeouts, and error handling become custom operational code.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge Pipes、SQS source、filter、target、DLQの公式説明を確認する。
What to confirm
自作ポーラーとPipesの責務分担を説明できる。
Key points
- EventBridge Pipes
- SQS
- DLQ
- Visibility timeout
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
At-least-once processing
A message can be delivered again, so target actions should be idempotent.
Failure isolation
Move repeatedly failing messages to a DLQ and replay them after correction.