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-kafka-connector-examples.git
The following commit(s) were added to refs/heads/master by this push:
new bd1d264 AWS2-IAM delete user sink example: Fixed refs
bd1d264 is described below
commit bd1d264010a6f265973849a7dbb1a3ab7cc3903d
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Nov 3 08:27:29 2020 +0100
AWS2-IAM delete user sink example: Fixed refs
---
aws2-iam/aws2-iam-sink-delete-user/README.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/aws2-iam/aws2-iam-sink-delete-user/README.adoc
b/aws2-iam/aws2-iam-sink-delete-user/README.adoc
index cd51c73..19ccddd 100644
--- a/aws2-iam/aws2-iam-sink-delete-user/README.adoc
+++ b/aws2-iam/aws2-iam-sink-delete-user/README.adoc
@@ -1,6 +1,6 @@
-= Camel-Kafka-connector AWS2 IAM Sink
+= Camel-Kafka-connector AWS2 IAM Sink for deleting user
-This is an example for Camel-Kafka-connector AWS2-IAM Sink
+This is an example for Camel-Kafka-connector AWS2-IAM Sink for deleting user
== Standalone
@@ -44,7 +44,7 @@ plugin.path=/home/oscerd/connectors
=== Setup the connectors
-Open the AWS2 IAM configuration file at
`$EXAMPLES/aws2-sqs/aws2-sqs-sink/config/CamelAWS2IAMSinkConnector.properties`
+Open the AWS2 IAM configuration file at
`$EXAMPLES/aws2-iam/aws2-iam-sink-delete-user/config/CamelAWS2IAMSinkConnector.properties`
[source]
----
@@ -68,11 +68,11 @@ and add the correct credentials for AWS.
=== Running the example
-Run the kafka connect with the SQS Sink connector:
+Run the kafka connect with the IAM Sink connector:
[source]
----
-$KAFKA_HOME/bin/connect-standalone.sh
$KAFKA_HOME/config/connect-standalone.properties
$EXAMPLES/aws2-sqs/aws2-sqs-sink/config/CamelAWS2IAMSinkConnector.properties
+$KAFKA_HOME/bin/connect-standalone.sh
$KAFKA_HOME/config/connect-standalone.properties
$EXAMPLES/aws2-iam/aws2-iam-sink-delete-user/config/CamelAWS2IAMSinkConnector.properties
----
You'll need to have the Camel user created in AWS IAM.
