Amazon Cognito User Pools source
This event source captures messages from an Amazon Cognito User Pool whenever a specific action, such as the creation of a new user, happens in the user identity pool.
apiVersion: sources.triggermesh.io/v1alpha1 kind: AWSCognitoUserPoolSource metadata: name: sample spec: arn: arn:aws:cognito-idp:us-west-2:123456789012:userpool/us-west-2_abcdefghi auth: credentials: accessKeyID: valueFromSecret: name: awscreds key: aws_access_key_id secretAccessKey: valueFromSecret: name: awscreds key: aws_secret_access_key sink: ref: apiVersion: eventing.triggermesh.io/v1alpha1 kind: RedisBroker name: triggermesh
Alternatively you can use an IAM role for authentication instead of an access key and secret, for Amazon EKS only:
To setup an IAM role for service accounts, please refer to the official AWS documentation.
Events produced have the following attributes:
- Schema of the
See the Kubernetes object reference for more details.
- Amazon Cognito User Pool
- Amazon Resource Name (ARN)
- API Credentials
Amazon Cognito User Pool
If you don't already have an Amazon Cognito User Pool, create one by following the instructions in the Getting started with User Pools guide.
Amazon Resource Name (ARN)
A fully qualified ARN is required to uniquely identify the Amazon Cognito User Pool.
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:
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
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 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 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 to it.
As an example, the following policy contains the permissions required by the TriggerMesh Amazon Cognito User Pool event source to list users in any user pool associated with the AWS account: