AWS Lambda target
Sends events to an AWS Lambda function.
With tmctl
:
tmctl create target awslambda --arn <arn> --auth.credentials.accessKeyID <access key> --auth.credentials.secretAccessKey <secret key>
On Kubernetes:
Secret
apiVersion: v1
kind: Secret
metadata:
name: aws
type: Opaque
stringData:
AWS_ACCESS_KEY_ID: "<AWS Access Key ID>"
AWS_SECRET_ACCESS_KEY: "<AWS Secret Access Key>"
Target
apiVersion: targets.triggermesh.io/v1alpha1
kind: AWSLambdaTarget
metadata:
name: triggermesh-aws-lambda
spec:
arn: arn:aws:lambda:us-west-2:043455440429:function:snslistener
auth:
credentials:
accessKeyID:
valueFromSecret:
name: aws
key: AWS_ACCESS_KEY_ID
secretAccessKey:
valueFromSecret:
name: aws
key: AWS_SECRET_ACCESS_KEY
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.
There is an optional toggle flag indicating if the full CloudEvent should be sent to the lambda function. By default, this is disabled which means only the event payload will be sent.
Accepts events of any type.
Responds with events with the following attributes:
- type
io.triggermesh.targets.aws.lambda.result
- source
arn:aws:lambda:...
, the Lambda's ARN value as configured by the target - Schema of the
data
attribute:
You can test the Target by sending it an event using curl
:
curl -v http://triggermesh-aws-lambda.default.svc.cluster.local \
-X POST \
-H "Content-Type: application/json" \
-H "Ce-Specversion: 1.0" \
-H "Ce-Type: dev.knative.source.aws" \
-H "Ce-Source: awesome/instance" \
-H "Ce-Id: 536808d3-88be-4077-9d7a-a3f162705f79" \
-d '{"greeting":"Hi from TriggerMesh"}'
See the Kubernetes object reference for more details.
Prerequisite(s)
- AWS API key and secret
- ARN for the Lambda to invoke
For more information about using AWS Lambda, please refer to the AWS documentation.