-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
Cannot send message to cross account FIFO SQS queue #938
Comments
@tomazfernandes perhaps we can give users option to configure the value for |
Sure. From the top of my mind, we could have a
And then Makes sense? |
It does! |
Cool! @ZhongXiLu, what do you think? Would you be interested in opening a PR with this change? |
@tomazfernandes Sure, I'll take a look 👍 |
Hi All, After migrating from Spring cloud 2 to 3.0.3.I am getting below error 2023-12-08T11:29:14.838+11:00 ERROR 1 --- [nio-8080-exec-1] c.g.t.d.s.s.SqsDataLoaderMessageSender : Error in calculation java.util.concurrent.CompletionException: io.awspring.cloud.sqs.QueueAttributesResolvingException: Error resolving attributes for queue tie-super-calc20230716111832302200000001.fifo with strategy CREATE and queueAttributesNames [ContentBasedDeduplication] With spring cloud 2,it was working fine.But after migration,getting above error does anyone has any idea? |
…ing#938) Resolves awspring#938 Update documentation Bugfix
…ing#938) Resolves awspring#938 Update documentation Bugfix
Hi Team, |
Type: Bug
Component:
SQS
Describe the bug
Whenever I try to send messages to a FIFO SQS queue in another AWS account, it results in following error:
Value ContentBasedDeduplication for parameter Attribute.Name is invalid. Reason: Only owners can access specified attribute.
It seems retrieving the
ContentBasedDeduplication
queue attribute does not work for a cross-account SQS queue, see https://github.com/awspring/spring-cloud-aws/blob/main/spring-cloud-aws-sqs/src/main/java/io/awspring/cloud/sqs/operations/SqsTemplate.java#L265.I'm using spring cloud version 3.0.2.
The bug seems to be introduced since 3.0.1 through this PR: #799.
Sample
The text was updated successfully, but these errors were encountered: