Setting up real-time event delivery

In addition to event file notifications, you can stream event notifications and data in real time through an integration channel. This guide explains what Pismo configures and what you need to configure for each delivery method.

Choose your cloud provider below and follow the corresponding tutorial.

AWS: Real-time with Amazon Simple Notification Service (SNS)

The following architecture delivers event notifications to your AWS account.

Pismo configuration: Pismo creates an Identity Access Management Role (IAM) Role that publishes events to your Amazon SNS topic.

What you need to do: Follow the AWS SNS event configuration tutorial to set up Amazon SNS for real-time event delivery.

📘

All primary event fields except the data field are sent as SNS message attributes. This allows you to create filtered subscriptions based on event domains and event types.

AWS: Real-time delivery with Amazon EventBridge

Pismo configuration: Pismo creates an AWS IAM role that publishes events to your Amazon EventBridge event bus.

What you need to do: Follow the AWS EventBridge Event Configuration Tutorial to set up EventBridge for real-time event delivery..

Google Cloud: Real-time delivery with Pub/Sub

The following architecture delivers event notifications to your Google Cloud account.

Pismo configuration: Pismo creates an IAM service account that publishes events to your Pub/Sub topic.

What you need to do: Follow the GCP event configuration tutorial to set up Pub/Sub for real-time event delivery..

Azure: Real-time delivery with Service Bus

The following architecture delivers event notifications to your Microsoft Azure account.

Pismo configuration: Pismo creates a service principal accesses your Azure Service Bus namespace and publishes events.

What you need to do: Follow the Azure event configuration tutorial to set up Azure Service Bus for real-time event delivery..

Confluent cloud: Real-time delivery with Kafka

Pismo configuration: Pismo produces events directly to your Confluent Cloud Kafka topic.

What you need to do: Follow the Confluent event configuration tutorial to set up real-time event delivery..

HTTP webhook (beta): Real-time delivery with HTTPS POST

Pismo configuration: Pismo sends encrypted events via HTTPS POST to your endpoint using Visa-compliant JWE/JWS standards.

Your configuration: Follow the Pismo data platform – HTTP integration guide (beta) to configure your endpoint for real-time event delivery.

Validate the integration

Each provider-specific tutorial includes tools and procedures to help you verify your integration, including:

• Manual validation commands
• Diagnostic scripts that check authentication, permissions, resources, and connectivity

For validation instructions, see the guide for your selected provider.

⚠️

Retry and retention policy: To ensure ecosystem stability, the Pismo platform applies retry limits. Events that exceed the retry threshold are moved to controlled retention and can be redelivered upon request, as long as they are within the 24-hour retention window.

📘

Need Pismo-specific details? Information such as Pismo's AWS Account ID, single-tenant SFTP endpoints, consumer role ARNs, or external IDs can be obtained from your Technical Account Manager (TAM) or the Implementation Engineer assigned to your project.