Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update SQS Source blog #6162

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Update SQS Source blog #6162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions blog/docs/articles/consuming_sqs_data_with_integrationsource.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,8 @@ metadata:
spec:
aws:
sqs:
queueNameOrArn: "my-queue"
region: "my-queue"
arn: "my-queue"
region: "my-region"
visibilityTimeout: 20
auth:
secret:
Expand All @@ -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

Expand Down
Loading