Amazon SNS target
Sends event to Amazon SNS.
With tmctl
:
tmctl create target awssns --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: AWSSNSTarget
metadata:
name: triggermesh-aws-sns
spec:
arn: arn:aws:sns:us-west-2:<PROJECT_ID>:tmtest
auth:
credentials:
accessKeyID:
valueFromSecret:
name: aws
key: AWS_ACCESS_KEY_ID
secretAccessKey:
valueFromSecret:
name: aws
key: AWS_SECRET_ACCESS_KEY
When TriggerMesh is running on Amazon EKS, you can use an IAM role for authentication rather than an access key and secret. In this case, TriggerMesh will generate a Kubernetes service account for you that will leverage this IAM role. You also have the option of specifying your own service account name, and if a service account with the same name already exists and it is already managed by the TriggerMesh controller, then it will be reused. By reusing the same serivce account in this way, you can avoid having to create many STS trust relationships for each generated service account.
For more details on authenticating with AWS, please take a look at our dedicated guide on AWS credentials.
There is an optional toggle flag indicating if the full CloudEvent should be sent to SNS. 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.sns.result
- source
arn:aws:sns:...
, the SNS ARN value as configured by the target
See the Kubernetes object reference for more details.
Prerequisite(s)
- AWS API key and secret
- ARN for the SNS topic to invoke
For more information about using AWS Simple Notification Service, please refer to the AWS documentation.