docs/aws_sqs_queue: Timeout with incompatible arguments #41590
Merged
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.
Description
SQS has an unusual behavior where certain misconfigurations cause it to hang indefinitely rather than return an error. Specifically, creating or updating an
aws_sqs_queue
results in atimeout while waiting
error if:kms_data_key_reuse_period_seconds
is set to a non-default value,sqs_managed_sse_enabled
isfalse
(explicitly or by default), andkms_master_key_id
is not set.While
resourceQueueCustomizeDiff
already handleskms_data_key_reuse_period_seconds
in some cases, we don't modify configurations to prevent this hanging behavior. Instead of enforcing a change, this PR updates the documentation to make users aware of the issue. We could also connectkms_data_key_reuse_period_seconds
,sqs_managed_sse_enabled
, andkms_master_key_id
to provide invalid configuration errors.Relations
Relates #41234
References
Output from Acceptance Testing
N/A