Skip to content


SQS event-source listens to messages on AWS SQS queue and helps sensor trigger workloads.

Event Structure

The structure of an event dispatched by the event-source over the eventbus looks like following,

            "context": {
              "type": "type_of_event_source",
              "specversion": "cloud_events_version",
              "source": "name_of_the_event_source",
              "id": "unique_event_id",
              "time": "event_time",
              "datacontenttype": "type_of_data",
              "subject": "name_of_the_configuration_within_event_source"
            "data": {
             "messageId": "message id",
             // Each message attribute consists of a Name, Type, and Value. For more information,
             // see Amazon SQS Message Attributes
             // (
             // in the Amazon Simple Queue Service Developer Guide.
             "messageAttributes": "message attributes", 
               "body": "Body is the message data",


  1. Create a queue called test either using aws cli or AWS SQS management console.

  2. Fetch your access and secret key for AWS account and base64 encode them.

  3. Create a secret called aws-secret as follows.

    apiVersion: v1
    kind: Secret
      name: aws-secret
    type: Opaque
      accesskey: <base64-access-key>
      secretkey: <base64-secret-key>
  4. Deploy the secret.

    kubectl -n argo-events apply -f aws-secret.yaml
  5. Create the event source by running the following command.

    kubectl apply -n argo-events -f
  6. Inspect the event-source pod logs to make sure it was able to subscribe to the queue specified in the event source to consume messages.

  7. Create the sensor by running the following command.

    kubectl apply -n argo-events -f
  8. Dispatch a message on sqs queue.

    aws sqs send-message --queue-url --message-body '{"message": "hello"}'
  9. Once a message is published, an argo workflow will be triggered. Run argo list to find the workflow.


Please read the FAQ.

Back to top