From e167e7f77ce74c1ff97e4dce4811bd1a98a84728 Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Mon, 25 Nov 2024 17:51:14 +0100 Subject: [PATCH] Update SQS Source blog Signed-off-by: Matthias Wessendorf --- .../articles/consuming_sqs_data_with_integrationsource.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/blog/docs/articles/consuming_sqs_data_with_integrationsource.md b/blog/docs/articles/consuming_sqs_data_with_integrationsource.md index 2c1fc630dab..7bcab008f98 100644 --- a/blog/docs/articles/consuming_sqs_data_with_integrationsource.md +++ b/blog/docs/articles/consuming_sqs_data_with_integrationsource.md @@ -38,8 +38,8 @@ metadata: spec: aws: sqs: - queueNameOrArn: "my-queue" - region: "my-queue" + arn: "my-queue" + region: "my-region" visibilityTimeout: 20 auth: secret: @@ -52,7 +52,7 @@ spec: name: my-broker ``` -The `IntegrationSource` has an `aws` field, for defining different Amazon Web Services, such as `s3`, `ddb-streams` or like in this case `sqs`. Underneath the `aws` property is also a reference to a _Kubernetes Secret_, which contains the credentials for connecting to AWS. All SQS notifications are processed by the source and being forwarded as CloudEvents to the provided `sink` +The `IntegrationSource` has an `aws` field, for defining different Amazon Web Services, such as `s3`, `ddbStreams` or like in this case `sqs`. Underneath the `aws` property is also a reference to a _Kubernetes Secret_, which contains the credentials for connecting to AWS. All SQS notifications are processed by the source and being forwarded as CloudEvents to the provided `sink` !!! note