Document Amazon S3 source

Author: antoineco

docs/images/awss3-source/after-creation-1.png

@@ -46,10 +46,10 @@ arn:aws:codecommit:{awsRegion}:{awsAccountId}:{repositoryName}
 
 ### API Credentials
 
-The TriggerMesh AWS CodeCommit event source authenticates calls to the AWS CodeCommit API using an [Access
-Key][accesskey]. The page at this link contains instructions to create an access key when signed either as the root user
-or as an IAM user. Take note of the **Access Key ID** and **Secret Access Key**, they will be used to create an instance
-of the event source.
+The TriggerMesh event source for Amazon CodeCommit authenticates calls to the AWS API using AWS Access Keys. The page
+[Understanding and getting your AWS credentials][accesskey] contains instructions to create access keys when signed-in
+either as the root user or as an IAM user. Take note of the **Access Key ID** and **Secret Access Key**, they will be
+used to create an instance of the event source.
 
 It is considered a [good practice][iam-bestpractices] to create dedicated users with restricted privileges in order to
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching

docs/images/awss3-source/arn-region-1.png

@@ -1,26 +1,30 @@
-# Event source for AWS Cognito User Pool
+# Event source for AWS Cognito User Pools
 
-This event source captures messages from an [AWS Cognito User Pool ][cup-docs] whenever a specific action, such as the creation of a new user, happens in the user identity pool.
+This event source captures messages from an [AWS Cognito User Pool][cup-docs] whenever a specific action, such as the
+creation of a new user, happens in the user identity pool.
 
 ## Prerequisites
 
 ### AWS Cognito User Pool
 
-If you don't already have an AWS Cognito User Pool, create one by following the instructions in the [Getting started with User Pools][cup-getting-started] guide.
+If you don't already have an AWS Cognito User Pool, create one by following the instructions in the [Getting started
+with User Pools][cup-getting-started] guide.
 
 ### Amazon Resource Name (ARN)
 
 A fully qualified ARN is required to uniquely identify the AWS Cognito User Pool.
 
 ![User Pool ARN](../images/awscognitouserpool-source/userpool-arn.png)
 
-As shown in the above screenshot, you can obtain the ARN of a User Pool from the AWS console. It typically has the following format:
+As shown in the above screenshot, you can obtain the ARN of a User Pool from the AWS console. It typically has the
+following format:
 
 ```
 arn:aws:cognito-idp:{awsRegion}:{awsAccountId}:userpool/{poolId}
 ```
 
-Alternatively you can also use the [AWS CLI][aws-cli]. The following command retrieves the ARN of a User Pool in the `us-west-2` region which has the pool id `us-west-2_fak3p001B`.
+Alternatively you can also use the [AWS CLI][aws-cli]. The following command retrieves the ARN of a User Pool in the
+`us-west-2` region which has the pool id `us-west-2_fak3p001B`.
 
 ```console
 $ aws --region us-west-2 cognito-idp describe-user-pool --user-pool-id us-west-2_fak3p001B
@@ -36,11 +40,17 @@ $ aws --region us-west-2 cognito-idp describe-user-pool --user-pool-id us-west-2
 
 ### API credentials
 
-The TriggerMesh AWS Cognito UserPool event source authenticates calls to the AWS Cognito API using an [Access Key][accesskey]. The page at this link contains instructions to create an access key when signed either as the root user or as an IAM user. Take note of the **Access Key ID** and **Secret Access Key**, they will be used to create an instance of the event source.
+The TriggerMesh event source for Amazon Cognito User Pools authenticates calls to the AWS API using AWS Access Keys. The
+page [Understanding and getting your AWS credentials][accesskey] contains instructions to create access keys when
+signed-in either as the root user or as an IAM user. Take note of the **Access Key ID** and **Secret Access Key**, they
+will be used to create an instance of the event source.
 
-It is considered a [good practice][iam-bestpractices] to create dedicated users with restricted privileges in order to programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching [IAM Policies][iam-policies] to it.
+It is considered a [good practice][iam-bestpractices] to create dedicated users with restricted privileges in order to
+programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching
+[IAM Policies][iam-policies] to it.
 
-As an example, the following policy contains the permissions required by the TriggerMesh AWS Cognito User Pool event source to list users in any user pool associated with the AWS account:
+As an example, the following policy contains the permissions required by the TriggerMesh AWS Cognito User Pool event
+source to list users in any user pool associated with the AWS account:
 
 ```json
 {
@@ -67,16 +77,19 @@ Open the Bridge creation screen and add a source of type `AWS Cognito User Pool`
 
 In the Source creation form, give a name to the event source and add the following information:
 
-* [**Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret Access Key to communicate with the AWS SQS API, as described in the previous sections.
+* [**Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret
+  Access Key to communicate with the AWS SQS API, as described in the previous sections.
 * [**AWS ARN**][arn]: ARN of the User Pool, as described in the previous sections.
 
 ![Source form](../images/awscognitouserpool-source/source-cognito-userpool-form.png)
 
-After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining components to the Bridge, then submit it.
+After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining
+components to the Bridge, then submit it.
 
 ![Bridge overview](../images/awscognitouserpool-source/bridge-form-target.png)
 
-A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the AWS Cognito User Pool.
+A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the AWS
+Cognito User Pool.
 
 ![Bridge status](../images/awscognitouserpool-source/bridge-status.png)
 

docs/images/awss3-source/create-bridge-1.png

@@ -45,10 +45,10 @@ $ aws dynamodb describe-table --table-name triggermeshtest --region us-west-2
 
 ### API Credentials
 
-The TriggerMesh AWS DynamoDB event source authenticates calls to the AWS DynamoDB API using an [Access Key][accesskey].
-The page at this link contains instructions to create an access key when signed either as the root user or as an IAM
-user. Take note of the **Access Key ID** and **Secret Access Key**, they will be used to create an instance of the event
-source.
+The TriggerMesh event source for Amazon DynamoDB authenticates calls to the AWS API using AWS Access Keys. The page
+[Understanding and getting your AWS credentials][accesskey] contains instructions to create access keys when signed-in
+either as the root user or as an IAM user. Take note of the **Access Key ID** and **Secret Access Key**, they will be
+used to create an instance of the event source.
 
 It is considered a [good practice][iam-bestpractices] to create dedicated users with restricted privileges in order to
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching