This pattern demonstrates how to use the Adobe I/O Events integration with Amazon EventBridge to process/route events from Adobe with AWS Lambda. This pattern is leveraging the Adobe I/O Events integration with Amazon EventBridge to send order events from the customer's Adobe account to their AWS account, via an Amazon EventBridge Partner event bus. Once the Adobe I/O events are in the customer's account, an Amazon EventBridge rule routes updated product events to a downstream Lambda function. In a real-world use case, the Lambda function could transform the event, send it to a downstream application, archive it in a warehouse service, or send a notification email to a customer using SES. Amazon CloudWatch log groups are provisioned for debugging and auditing. This pattern deploys two EventBridge rules, one Lambda function, and two CloudWatch log groups.

Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/patterns/adobe-eventbridge-lambda

Important: this application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the AWS Pricing page for details. You are responsible for any AWS costs incurred. No warranty is implied in this example.

• Create an AWS account if you do not already have one and log in. The IAM user that you use must have sufficient permissions to make necessary AWS service calls and manage AWS resources.
• AWS CLI installed and configured
• Git Installed
• AWS CDK CLI (AWS CDK) installed
• Create an Adobe Developer Account if you do not already have one and log in. While the Adobe Developer Account is free, if you wanted to send custom events from Developer App Builder, it is free only for Adobe enterprise customers or partners who want to extend and integrate Adobe Experience Platform and Adobe Experience Cloud solutions. Currently, it is not available to individual developers who are not part of an Adobe enterprise or partner organization.
• Set up the Adobe Amazon EventBridge integration if you have not already configured the integration.

1. Create a new directory, navigate to that directory in a terminal and clone the GitHub repository:

   git clone https://github.com/aws-samples/serverless-patterns
   

2. Change directory to the pattern directory:

   cd adobe-eventbridge-lambda
   

3. From the command line, use AWS CDK to deploy the AWS resources for the pattern as specified in the app.py file. A command-line argument is needed to deploy the CDK stack, "adobeEventBusName". This argument should be the name of the SaaS event bus associated with your Adobe partner event source.

   cdk deploy --parameters adobeEventBusName=SAAS_EVENT_BUS_NAME_HERE
   

4. Note the outputs from the CDK deployment process. These contain the resource names and/or ARNs which are used for testing. This stack will output the name of the Lambda function deployed for testing to the CLI. See the example below.

Outputs:
AdobeIntegrationStack.AdobeProcessSpecificEventsLambdaOutput = AdobeIntegrationStack-AdobeProcessOrderEventsLambd....

This service interaction uses an existing Adobe SaaS integration in the customer's AWS account. If you do not have the Adobe SaaS integration set up in your AWS account, please set it up before deploying this pattern. View the integration on Adobe's developer site.

This pattern demonstrates how to:

1. Write EventBridge rules that match Adobe's event pattern
2. Send events from Adobe's EventBridge integration to Amazon CloudWatch for logging and debugging
3. Transform Adobe I/O events using AWS Lambda and how to connect to other services

See the below architecture diagram from the data flow of this pattern.

The event.json file included in this pattern is a sample EventBridge event from Adobe. This event can be used to test the Lambda function and EventBridge rules deployed by this pattern.

To test the Lambda function via the CLI, copy and paste the following command, replacing the variables in <> with your own values:

aws lambda invoke --function-name <AdobeIntegrationStack-AdobeProcessOrderEventsLambd-....> --payload file://event.json --cli-binary-format raw-in-base64-out response.json

You should receive a response that looks like:

{
    "StatusCode": 200,
    "ExecutedVersion": "$LATEST"
}

The command should have create a response.json file in your directory. If you open this file, you see the output of the Lambda function.

You cannot put events on the Adobe event bus, only Adobe can publish events to this event bus. To test that the EventBridge rules deployed by this pattern were successfully deployed, follow these instructions:

1. Navigate to the Amazon EventBridge console. Select "Rules".

2. From the Event bus list, choose the SaaS event bus associated with your Adobe partner event source.

3. From the Rules list, select the "AdobeIntegrationStack-AdobeSpecficEventsRule54D..."

4. Choose "Edit" to enter the rule editor. Click through to "Step 2. Build Event Pattern."

5. Scroll down to "Sample event - optional." Select "Enter my own," and delete the pre-populated event. Copy the contents of event.json into the event editor.

6. Scroll down to "Event pattern." Choose "Test Pattern."

You should see a green box appear that says "Sample event matched the event pattern." This means that the rule will successfully route incoming events to the AWS Lambda function.

1. Delete the stack

   cdk destroy

Copyright 2024 Amazon.com, Inc. or its affiliates. All Rights Reserved.

SPDX-License-Identifier: MIT-0