fix: Adjust SQS visibility timeout to appropriate value #451
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.
Issue #, if available:
Description of changes:
When connecting SQS with Lambda, it is recommended to set the visibility timeout to six times the Lambda function's timeout value. The visibility timeout should be at least longer than the Lambda function's timeout multiplied by the number of retries.
https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html
(JP)
SQSとLambdaを接続する場合にはLambdaのタイムアウトの6倍の値を可視性タイムアウトにすることが推奨されています。
少なくともLambdaのタイムアウト*試行回数より長い可視性タイムアウトを取る必要があります。
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.