-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Prepper documentation for the SNS to SQS fan out pattern in S3 #3915
Data Prepper documentation for the SNS to SQS fan out pattern in S3 #3915
Conversation
…pper. Signed-off-by: David Venable <[email protected]>
Looking over this now. |
|
||
To meet the scale of logs produced in S3, some users require multiple SQS queues for their logs. You can use the [Amazon Simple Notification Service](https://docs.aws.amazon.com/sns/latest/dg/welcome.html) (SNS) to route event notifications from S3 to an SQS [fanout pattern](https://docs.aws.amazon.com/sns/latest/dg/sns-common-scenarios.html). Using SNS, all S3 event notifications go directly to a single SNS topic, where you can subscribe to multiple SQS queues. | ||
|
||
To make sure that Data Prepper can parse the event from the SNS topic directly, configure [raw message delivery](https://docs.aws.amazon.com/sns/latest/dg/sns-large-payload-raw-message-delivery.html) on the SNS to SQS subscription. If you want Data Prepper to ignore an SQS queue that sends notifications to your SNS topic, do not enable raw message delivery those queues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want Data Prepper to ignore an SQS queue
I don't think this properly conveys the situation. Data Prepper isn't ignoring these SQS queues. They are not being used at all by Data Prepper. Also, the user can configure those other queues to use raw message delivery or not. It doesn't affect Data Prepper and Data Prepper doesn't affect them.
The point of my original wording was to help with the objection that setting raw message delivery will affect other consumers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this?
"When raw message delivery is not enabled on an SQS queue, Data Prepper does not use that SQS queue."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not sure if that really conveys what I'm trying to say here.
This is my original text:
The raw message delivery option is on the connection between SNS and SQS.
Thus, you can have some SQS queues which do not enable raw message delivery.
Using Data Prepper will not interfere with those queues.
Perhaps we can simply say:
Setting this option will not affect other SQS queues which are subscribed to that SNS topic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Naarcha-AWS Approved with noted changes. Thanks!
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
…3915) * Adds documentation on how to use the SNS to SQS fan out with Data Prepper. Signed-off-by: David Venable <[email protected]> * Grammar edits. * Update s3-logs.md * Update _data-prepper/common-use-cases/s3-logs.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> * Update _data-prepper/common-use-cases/s3-logs.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> --------- Signed-off-by: David Venable <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> Co-authored-by: Nathan Bower <[email protected]> (cherry picked from commit a9a47ed) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…3915) (#4082) * Adds documentation on how to use the SNS to SQS fan out with Data Prepper. * Grammar edits. * Update s3-logs.md * Update _data-prepper/common-use-cases/s3-logs.md * Update _data-prepper/common-use-cases/s3-logs.md --------- (cherry picked from commit a9a47ed) Signed-off-by: David Venable <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Naarcha-AWS <[email protected]> Co-authored-by: Nathan Bower <[email protected]>
…pensearch-project#3915) * Adds documentation on how to use the SNS to SQS fan out with Data Prepper. Signed-off-by: David Venable <[email protected]> * Grammar edits. * Update s3-logs.md * Update _data-prepper/common-use-cases/s3-logs.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> * Update _data-prepper/common-use-cases/s3-logs.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> --------- Signed-off-by: David Venable <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> Co-authored-by: Nathan Bower <[email protected]>
Description
Some users have hit an issue using Data Prepper with an SNS/SQS fan out. This can be overcome and this documentation change conveys what a user needs to do for it.
Issues Resolved
N/A
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.