You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/11/27 11:19:38 UTC
[camel] 02/02: Regen catalog and website docs
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1cfdb1b31db7bcb4f190e9ff218a82f23da425e6
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Nov 27 12:18:46 2020 +0100
Regen catalog and website docs
---
.../camel/catalog/docs/aws2-sns-component.adoc | 50 ++++++++++++++++++++++
.../modules/ROOT/pages/aws2-sns-component.adoc | 50 ++++++++++++++++++++++
2 files changed, 100 insertions(+)
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sns-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sns-component.adoc
index ba551be..0e34990 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sns-component.adoc
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sns-component.adoc
@@ -207,6 +207,56 @@ The component is capable of detecting the presence of an SnsClient bean into the
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
+== SNS FIFO
+
+SNS FIFO are supported. While creating the SQS queue you will subscribe to the SNS topic there is an important point to remember, you'll need to make possible for the SNS Topic to send message to the SQS Queue.
+
+This is clear with an example.
+
+Suppose you created an SNS FIFO Topic called Order.fifo and an SQS Queue called QueueSub.fifo.
+
+In the access Policy of the QueueSub.fifo you should submit something like this
+
+[source,bash]
+-------------------------------------------------
+{
+ "Version": "2008-10-17",
+ "Id": "__default_policy_ID",
+ "Statement": [
+ {
+ "Sid": "__owner_statement",
+ "Effect": "Allow",
+ "Principal": {
+ "AWS": "arn:aws:iam::780560123482:root"
+ },
+ "Action": "SQS:*",
+ "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo"
+ },
+ {
+ "Effect": "Allow",
+ "Principal": {
+ "Service": "sns.amazonaws.com"
+ },
+ "Action": "SQS:SendMessage",
+ "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo",
+ "Condition": {
+ "ArnLike": {
+ "aws:SourceArn": "arn:aws:sns:eu-west-1:780410022472:Order.fifo"
+ }
+ }
+ }
+ ]
+}
+-------------------------------------------------
+
+This is a critical step to make the subscription work correctly.
+
+=== SNS Fifo Topic Message group Id Strategy and message Deduplication Id Strategy
+
+When sending something to the FIFO topic you'll need to always set up a message group Id strategy.
+
+If the content-based message deduplication has been enabled on the SNS Fifo topic, where won't be the need of setting a message deduplication id strategy, otherwise you'll have to set it.
+
== Dependencies
Maven users will need to add the following dependency to their pom.xml.
diff --git a/docs/components/modules/ROOT/pages/aws2-sns-component.adoc b/docs/components/modules/ROOT/pages/aws2-sns-component.adoc
index 41d9e18..0c55e22 100644
--- a/docs/components/modules/ROOT/pages/aws2-sns-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws2-sns-component.adoc
@@ -209,6 +209,56 @@ The component is capable of detecting the presence of an SnsClient bean into the
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
+== SNS FIFO
+
+SNS FIFO are supported. While creating the SQS queue you will subscribe to the SNS topic there is an important point to remember, you'll need to make possible for the SNS Topic to send message to the SQS Queue.
+
+This is clear with an example.
+
+Suppose you created an SNS FIFO Topic called Order.fifo and an SQS Queue called QueueSub.fifo.
+
+In the access Policy of the QueueSub.fifo you should submit something like this
+
+[source,bash]
+-------------------------------------------------
+{
+ "Version": "2008-10-17",
+ "Id": "__default_policy_ID",
+ "Statement": [
+ {
+ "Sid": "__owner_statement",
+ "Effect": "Allow",
+ "Principal": {
+ "AWS": "arn:aws:iam::780560123482:root"
+ },
+ "Action": "SQS:*",
+ "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo"
+ },
+ {
+ "Effect": "Allow",
+ "Principal": {
+ "Service": "sns.amazonaws.com"
+ },
+ "Action": "SQS:SendMessage",
+ "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo",
+ "Condition": {
+ "ArnLike": {
+ "aws:SourceArn": "arn:aws:sns:eu-west-1:780410022472:Order.fifo"
+ }
+ }
+ }
+ ]
+}
+-------------------------------------------------
+
+This is a critical step to make the subscription work correctly.
+
+=== SNS Fifo Topic Message group Id Strategy and message Deduplication Id Strategy
+
+When sending something to the FIFO topic you'll need to always set up a message group Id strategy.
+
+If the content-based message deduplication has been enabled on the SNS Fifo topic, where won't be the need of setting a message deduplication id strategy, otherwise you'll have to set it.
+
== Dependencies
Maven users will need to add the following dependency to their pom.xml.