[Backport 3.4] Update AWS Lambda plugin documentation for optional timeout configurations#11840
Merged
github-actions[bot] merged 1 commit into3.4from Feb 4, 2026
Merged
Conversation
…tions (#11771) * Add read_timeout configuration documentation for AWS Lambda plugin - Add read_timeout field to processor configuration table and example - Add client configuration options to sink documentation including read_timeout - Documents new configurable read timeout for Lambda function calls Signed-off-by: Aiswarya Sadananda Rao <aiswarao@amazon.com> * Update AWS Lambda plugin documentation for optional timeout configurations - Add api_call_attempt_timeout as optional configuration parameter - Update read_timeout to be optional (uses AWS SDK defaults when not specified) - Add timeout configuration guidance section explaining AWS SDK timeout hierarchy - Update examples to show optional timeout usage for long-running Lambda functions - Provide clear guidance on when to configure each timeout parameter Documentation updates support the new optional timeout features in Data Prepper AWS Lambda plugin. Signed-off-by: Aiswarya Sadananda Rao <aiswarao@amazon.com> * Doc review Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Apply suggestions from code review Signed-off-by: Nathan Bower <nbower@amazon.com> --------- Signed-off-by: Aiswarya Sadananda Rao <aiswarao@amazon.com> Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> Signed-off-by: Nathan Bower <nbower@amazon.com> Co-authored-by: Aiswarya Sadananda Rao <aiswarao@amazon.com> Co-authored-by: Fanit Kolchina <kolchfa@amazon.com> Co-authored-by: Nathan Bower <nbower@amazon.com> (cherry picked from commit e1c71bb) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
opensearch-trigger-bot
bot
requested review from
AMoo-Miki,
dlvenable,
epugh,
kolchfa-aws,
natebower and
sumobrian
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport e1c71bb from #11771.