---
Title: Configure streaming
URL Source: https://company-skill.com/p/eb/eb-configure-streaming
Language: en
Description: You want to set up a real-time pipeline that moves events from a source (like Kafka, RabbitMQ, or MQTT) to a destination (like OSS, Function Compute, or another message queue), with options to…
---

# Configure streaming

Part of **EventBridge**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to set up a real-time pipeline that moves events from a source (like Kafka, RabbitMQ, or MQTT) to a destination (like OSS, Function Compute, or another message queue), with options to filter, transform, and monitor the flow.

- How to create a Kafka connector?
- Can I stream RabbitMQ data to EventBridge?

## Decision Tree

Pick the best path for your situation:

- **If** you need to integrate event streaming into an automated data platform or CI/CD pipeline using code → Use API (go to *eb/eb-event-streaming*)
- **If** you want to visually create a connector for Kafka, RabbitMQ, or OSS and monitor its status in a dashboard → Use (go to *eb/eb-event-streaming*)
- **If** you require precise control over filtering rules, retry policies, or batch parameters via JSON configuration → Use API (go to *eb/eb-event-streaming*)
- **Otherwise (default)** → Use — it’s faster for one-off setups and provides built-in monitoring for Connectors and Event Streams.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| API | high | Yes | Yes | CapacityUnitMode EventNumMode | `eb/api/eb-event-streaming` |
| Kafka/RabbitMQ/OSS | medium | No | No | 30 60 cold start latency | `eb/guide/eb-event-streaming` |

## Path Details

### Path 1: API 

**Brief Description**: EventBridge Event Streaming API HTTP . It supports defining a **Source** (e.g., RabbitMQ) and a **Sink**, and uses APIs like "Configure RabbitMQ Source for Event Streaming". All operations are synchronous and require manual handling of authentication and payload formatting.

**Key technical facts**:
- Billing: API CapacityUnitMode EventNumMode
- Auth method: Bearer Token Authorization: Bearer <your_api_key>Authorization: acs <AccessKeyID>:<Signature>
- Regions available: cn-hangzhou, cn-shanghai, cn-beijing

- RabbitMQRocketMQMNS /

- API JSON 

### Path 2: Console / Dashboard
**Best For**: Kafka/RabbitMQ/OSS 

**Brief Description**: The EventBridge console provides a graphical interface to manage **Connectors** and **Event Streams**. You can use **Create Connector** or **Create Event Stream** wizards to configure sources like Kafka and sinks like **OSS Bucket**, specifying **Storage Path**, **Time Partition**, **Batch size**, and network settings. Built-in **Monitoring** shows connector health and metrics.

**Key technical facts**:
- Billing: OSS sink 1000 Function Compute 100 
- Cold start: 30 60 
- Auth method: SSO
- Prerequisites: EventBridge RAM / OSS Kafka VPC/vSwitch 

- Kafka Connect 

## FAQ

Q: Which path should I start with?
A: Start with **** if you’re setting up a single stream for Kafka, RabbitMQ, or OSS and want immediate visibility into status and metrics. Only choose the API path if you already have automation infrastructure.

Q: What if I need sub-second event delivery but used the console path?
A: You’ll hit latency due to **Batch Push** being enabled by default (100 messages or 3-second window). This batching may violate real-time requirements unless you adjust **Batch Push Interval** and **Batch size**—but even then, cold start adds 30–60 seconds.

Q: What if I need to update the source type after creating a stream in the console?
A: You’ll be blocked—you cannot modify core settings like source type post-creation. You must delete and recreate the entire **Event Stream**, losing historical state and requiring reconfiguration of **OSS Bucket**, **Storage Path**, and **Time Partition**.

Q: Can I use the API path to configure an OSS sink with time-based partitioning?
A: Yes—the API allows full control over **Sink** parameters including **Time Partition** and **Storage Path**, but you must encode these correctly in JSON and handle authentication manually.

Q: What if I exceed the RabbitMQ API rate limit of 100 requests/minute?
A: Subsequent calls will be throttled or rejected. If you chose the API path for high-frequency updates (e.g., dynamic scaling), you’ll need to implement client-side queuing or switch to less frequent batch updates.

Q: Does the console support all the same source types as the API?
A: Not necessarily—while both support Kafka and RabbitMQ, the API explicitly mentions MNS and . The console’s supported types are limited to those exposed in the **Create Connector** UI; undocumented types may only be accessible via API.

## Related queries

configure real time event streaming, real-time event stream, event streaming setup, stream events in real time, real time event pipeline, how to stream events, create event stream, event stream configuration, set up event streaming, event bridge streaming, stream to OSS, Kafka connector setup, Rabbi

---
Part of [EventBridge](https://company-skill.com/p/eb.md) · https://company-skill.com/llms.txt