amazon eventbridge integration

EventBridge and Lambda

Integrate Amazon EventBridge partner event sources with AWS Lambda

This Quick Start integrates Amazon EventBridge with Amazon Web Services (AWS) Lambda. Events are routed to an EventBridge event bus where a rule evaluates them and invokes an AWS Lambda function when a matching event occurs.

You can use this as a starter project to extend this integration for any scenario that can use AWS Lambda to run code.

EventBridge Lambda architecture diagram

This Quick Start was developed by
Amazon Web Services (AWS).

 See the source code for this Quick Start
  •  Deploy this EventBridge integration
  •  Deploy this EventBridge integration
  • Step 1                  If you don't already have an AWS account, sign up at https://aws.amazon.com, and sign in to your account. Getting an account automatically signs you up for EventBridge and other AWS services.
    Step 2           Configure your EventBridge software as a service (SaaS) integration, and note the event source name (e.g., aws.partner/example.com/1234567890/test-event-source). Before proceeding, ensure that your event source is listed as Pending.
    Step 3 Deploy the integration. Launch the AWS CloudFormation template. The deployment takes about 5 minutes to complete. EventBridge integrations are currently supported in all AWS commercial Regions.

    Configure your Amazon EventBridge SaaS Integration Partner event source and make note of the event source name (for example, aws.partner/example.com/1234567890/test-event-source).

    Configure your Amazon EventBridge SaaS Integration Partner event source and make note of the event source name (for example, aws.partner/example.com/1234567890/test-event-source).

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

    You are responsible for the cost of the AWS services and partner integrations used while running this Quick Start deployment.

    To post feedback, submit feature ideas, or report bugs, use the Issues section of the GitHub repository.