---
title: "PavedRoad Event Orchestrator With Wasabi"
slug: "how-do-i-use-pavedroad-event-orchestrator-with-wasabi"
updated: 2026-11-09T21:33:18Z
published: 2026-11-09T21:33:18Z
canonical: "docs.wasabi.com/how-do-i-use-pavedroad-event-orchestrator-with-wasabi"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PavedRoad Event Orchestrator With Wasabi

Wasabi has been validated with [PavedRoad](https://www.pavedroad.io)'s Event Orchestrator. [EventOrchestrator](https://www.pavedroad.io/pavedroad-event-orchestrator/) delivers Event Orchestration for the MultiCloud World, enabling businesses to easily reduce data costs without leaving services behind. To learn more about the PavedRoad—Wasabi joint solution, review [Multicloud Storage Management Made Easy](https://wasabi.com/blog/data-management/multicloud-storage-management-made-easy).

To use this product with Wasabi, follow the instructions below.

## Reference Architecture

![arch.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4414949676443.png)

## Requirements

- A PavedRoad account
- An active Wasabi account

## Introduction

The Event Orchestrator platform is a powerful tool for connecting all your cloud providers and platforms to quickly integrate or create new capabilities such as functions, workflows, or data processing. There are only three simple concepts you need to understand to get the event orchestrator working for you.

- Sources are inputs to the event orchestrator, such as events read from messaging services, information returned from API calls, or data retrieved from sources like log files. Examples of sources include GitHub, S3, Kafka, Slack, calendars, and many more.
- Triggers are actions taken in response to sources such as writing a message to a Slack channel, processing a video file, or writing to an event queue for other systems, such as AWS SNS. A single source can trigger any number of actions.
- A workflow can be applied to an event source, if needed, to handle any processing required before triggers are invoked. Typical workflow tasks include filtering, transforming data into the format required by the trigger, and aggregating source data.

## Creating a PavedRoad Account

You can set up your Event Orchestrator account with an existing social account, such as Google, GitHub, or Microsoft.

1. Open the [PavedRoad URL](https://eo.pavedroad.io) (https://eo.pavedroad.io) in your browser, or create a new account. When you open the URL, the following login screen will appear.

Click the **Sign up** link next to the message if you do not have an account.

![Picture1.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4415548774171.png)
2. Either use an existing email and select your password, or click on a social account provider to continue. When selecting a social login provider, a screen appears requesting permission for Event Orchestrator to read your name and profile information.

![Picture2.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4415549087131.png)
3. After logging in, you are asked to input your company information.

![Screen_Shot_2022-01-14_at_3.37.04_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4415536093851.png)

## Creating a Cloud Orchestration

Use the [Start Wasabi link](https://eo.pavedroad.io/startwasabi) (https://eo.pavedroad.io/startwasabi) to set up your first orchestration. This example polls Wasabi log buckets and then invokes an AWS Lambda function to generate MD5 checksums for any new content uploads. Adding checksums to files is a common anti-tampering technique.

The example has three simple steps: setting up API credentials, adding a Lambda function (Trigger), and setting up your Wasabi bucket Source.

![Screen_Shot_2022-01-14_at_3.40.04_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4415549170971.png)

## Setting Up API Credentials

Setting up API access is a one-time action for most use cases.

For AWS, log in to the console and select the Identity and Access Management (IAM) service. A user will be created who only has access to Lambda. Select Add users, enter a name, select Access key Programmatic access, enter a username, select Access key Programmatic access, and click **Next**.

![Picture3.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418290169499.png)

On the following screen, select the **attach existing policy** button and enter l**ambda** in the search box. Then select the **permission level** you want to give this user.

![Screen_Shot_2022-02-08_at_10.09.41_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418290182043.png)

Use the next button to proceed through the remaining options, then create the user. You will see the following information. Save the access key and secret.

![Screen_Shot_2022-02-08_at_10.11.10_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418283137691.png)

Log in to your Wasabi Console, select Users, and then use the Create User button. Create a user that represents the role for accessing your Wasabi buckets programmatically.

![Screen_Shot_2022-02-08_at_10.13.08_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418283155995.png)

Log in to your Wasabi Console, then select Users to grant both read and write access using the Full Access policy.

![Screen_Shot_2022-02-08_at_10.16.23_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418297737371.png)

After creating the user, save the access key and secret just like we did for AWS.

Go to the event orchestrator console, select providers, and click the NEW button.

![Screen_Shot_2022-02-08_at_10.20.29_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418290376987.png)

Enter your provider information. Enter the region where you created the credentials, and for Wasabi, specify the endpoint.

![Screen_Shot_2022-02-08_at_10.23.38_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418283349659.png)

*Note: This config example uses Wasabi’s us-west-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in* [*Service URLs for Wasabi's Storage Regions*](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabis-different-storage-regions).

Repeat these steps for AWS.

## Creating Your First Event Source

From the event orchestrator console, select the S3 Buckets menu item under the Sources menu. Then select the NEW button to create your first Wasabi source. The S3 bucket source polls an S3 bucket containing logs and then parses them. Use the filters option to limit which log lines trigger a response.

Enter the name of your Wasabi logging bucket, select the Wasabi provider you just created, and S3 for the log file format.

S3 logs have an API type, a method, and a resource type. For this example, we want events when a new file is created, so our values are REST, PUT, POST, and OBJECT.

Click **Add,** and the first source is complete.

Any time a new file is created, you can now trigger an action to happen (for example, log a message to a Slack channel or trigger an AWS Lambda function).

![Screen_Shot_2022-02-08_at_10.28.39_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418290488731.png)

### Adding a Lambda Function

For this use case, we’ve created a Python function that gets triggered by the source event you just created. The source code can be found in the [Start Wasabi wizard.](https://eo.pavedroad.io/startwasabi) In this example, we called our Lambda function pymd5. If you are new to creating Lambda functions, read more in [Create your first Lambda function](https://docs.aws.amazon.com/lambda/latest/dg/getting-started.html).

![Screen_Shot_2022-02-08_at_10.32.05_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418283441179.png)

## Adding a Trigger

Now that you have a function, you can create the trigger. In the Event Orchestrator control panel, click **AWS Lambda** from the Triggers menu. Then click **New** to create your first trigger.

There are four fields.

- A descriptive name for your trigger
- The name of the trigger in AWS
- The providers
- And the AWS region the trigger is in

![image.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/4418283491483.png)

The two cloud providers are connected.