Event-Driven Workflows with TriggerMesh and Amazon EventBridge

Mark Hinkle
Mark Hinkle
Jan 21, 2021
Event-Driven Workflows with TriggerMesh and Amazon EventBridge
Event-Driven Workflows with TriggerMesh and Amazon EventBridge

When Amazon launched EventBridge in July of 2019 here at TriggerMesh we saw it as a huge validation for our work on a cloud native integration platform. Our goal is to help organizations create workflows using real-time data to trigger workloads across cloud infrastructures. Amazon provided this capability within their ecosystem, but we saw it as necessary for the integration of services that augment AWS. We feel that providing a standardized way for application integration across all cloud services and applications is absolutely necessary to realize the benefits of cloud native integration. 

EventBridge does this within the Amazon ecosystem but we foresaw a need for doing this with workflows across other clouds and on-premises infrastructure. That’s why we added the capabilities to enable TriggerMesh to be a source to Amazon EventBridge allowing any event source, on-premises or from other clouds, to forward to Amazon EventBridge and trigger workflows there. 

In August of last year, we announced our integration with EventBridge to use sources from a variety of cloud events to trigger AWS workloads.  This unique capability means that TriggerMesh can act as a bridge to source events from literally anywhere into AWS, and use this external data to feed AWS services without writing a single line of code.

We accomplish this either in one of two ways. First, to deploy a generic HTTP webhook (HTTP event source) into TriggerMesh and use it as the entry point for external services. Alternatively, enterprises can use the catalog of available TriggerMesh integrations to source events from popular third-party services such as Salesforce, Confluent, or other cloud providers such as Microsoft Azure, the Google Cloud Platform, or the Oracle Cloud.

Event-Driven Worklows with TriggerMesh and Amazon EventBridge


So, what are some examples of what we have seen users doing with TriggerMesh?

  • A bank wanted to stream real-time changes from MongoDB Atlas to Amazon Web Services
  • A web application provider in the legal space wanted to create event syncs between Hasura GraphQL engine to EventBridge to trigger Step Functions on Lambda
  • Amazon Web Services users who want to trigger workloads on OpenShift

Combining the power of TriggerMesh and EventBridge, AWS users can easily connect SaaS, cloud, and on-premises applications with Amazon Lambda and cloud-native architectures without writing any additional code. You can modernize your legacy applications to the cloud and leverage your existing IT investment by integrating with Amazon EventBridge and triggering workloads on modern architecture. Accelerate developer productivity and provide consistency when integrating non-AWS services with AWS.

Cloud-native developers want to build applications that connect a distributed web of services. Amazon provides many of the most widely-used cloud services, and for integrations with legacy applications and with bespoke services like CRM (Salesforce and Zendesk), communications (Twilio/Sendgrid, Slack), and others, TriggerMesh is a powerful cloud native option. 


Related Posts

Join our newsletter

Subscribe to TriggerMesh newsletter. You'll get only the most important news about TriggerMesh