# eb-event-streaming

Part of **EB**

# EventBridge Event Streaming Console Guide

## Operations Overview

| Operation | Console Navigation Path | Prerequisites | Description |
|-----------|------------------------|---------------|-------------|
| Create OSS Sink Connector | Console > EventBridge > Connectors > Create Connector | An OSS bucket created in the OSS console | Create a connector to deliver streamed events to OSS objects |
| Create Apache Kafka Custom Connector | Console > EventBridge > Connectors > Create Connector | Active Apache Kafka instance with connectivity; EventBridge enabled | Create a custom connector for Apache Kafka integration |
| Manage Custom Kafka Connector Tasks | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; OSS bucket created; SAE activated; VPC/vSwitch created; ApsaraMQ for Kafka instance deployed | Create and manage custom ApsaraMQ for Kafka connector tasks |
| Monitor Kafka Connector Status | Console > EventBridge > Event Streams > [Target Connector] > Details > Monitoring | Custom Kafka connector task created; permissions to view details | View monitoring metrics and troubleshoot connector failures |
| Create RabbitMQ Connector | Console > EventBridge > Streaming Tasks > Create Task | EventBridge activated; ApsaraMQ for RabbitMQ resources created; OSS bucket created; SAE activated; VPC/vSwitch created; ApsaraMQ for Kafka instance deployed | Synchronize RabbitMQ data using the RabbitMQ Connector |
| Configure Kafka as Event Provider | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; Message Queue for Apache Kafka instance deployed | Add Message Queue for Apache Kafka as an event provider |
| Configure MQTT Event Source | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; Message Queue for MQTT instance running | Set up Message Queue for MQTT as an event source |
| Configure RabbitMQ as Event Stream Provider | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; ApsaraMQ for RabbitMQ instance running | Add ApsaraMQ for RabbitMQ as an event stream provider |
| Configure RocketMQ Offset Data Event Source | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; RocketMQ 5.x or 4.x instance created; topic created | Configure Message Queue for Apache RocketMQ offset data as event source |
| Configure RocketMQ as Event Source | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; RocketMQ 5.x or 4.x instance created; topic created | Create an event stream from RocketMQ |
| Configure DTS as Event Provider | Console > EventBridge > Event Streams > Create Event Stream | DTS change tracking task in NORMAL state; consumer group created; EventBridge activated | Configure Data Transmission Service as an event provider |
| Configure Event Bus as Source | Console > EventBridge > Event Streams > Add Event Source | EventBridge activated; required permissions granted | Use an event bus as an event stream source |
| Configure MNS as Event Stream Source | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; MNS queue created | Configure Message Service as an event stream source |
| Configure Self-managed Kafka as Event Source | Console > EventBridge > Event Streams > Create Event Source | EventBridge activated; Apache Kafka cluster deployed and accessible | Add self-managed Apache Kafka cluster as event source |
| Configure SLS as Event Stream Provider | Console > EventBridge > Event Streams > Create Event Stream | Log Service (SLS) activated; project and Logstore created; EventBridge activated | Create an event stream from Simple Log Service |
| Route Events to Kafka | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; Message Queue for Apache Kafka instance running | Route events to Message Queue for Apache Kafka |
| Route Events to RabbitMQ | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; ApsaraMQ for RabbitMQ instance running | Route events to ApsaraMQ for RabbitMQ |
| Route Events to RocketMQ | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; RocketMQ 5.x or 4.x instance created; topic created | Route events to Message Queue for RocketMQ |
| Route Events to Function Compute | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; Function Compute service and function created | Route events to Function Compute service |
| Route Events to SMQ | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; SMQ queue created | Route events to Simple Message Queue |
| Route Events to Simple Log Service | Console > EventBridge > Event Streams > Create Event Stream | Simple Log Service activated; project and logstore created; EventBridge activated | Route events to Simple Log Service |
| Event Transformation in Event Streams | Console > EventBridge > Event Transformation | Existing event bus configured; target service expecting specific payload | Transform event payload within event streams |
| Manage Event Streams | Console > EventBridge > Event Streams | EventBridge activated; required permissions granted | Create, edit, enable, disable, and delete event streams |
| View Event Stream Metrics | Console > EventBridge > Event Streams > Select stream > Monitoring | EventBridge activated; event stream created | View monitoring metrics for event streams |
| Create Kafka to RocketMQ Inflow Task | Console > EventBridge > Streaming Tasks > Create Task | RocketMQ instance running; Kafka instance deployed and running | Create a message inflow task from Kafka to RocketMQ |
| Create MQTT to RocketMQ Inflow Task | Console > EventBridge > Message Inflow Tasks > Create Task | ApsaraMQ for RocketMQ instance running; ApsaraMQ for MQTT instance running | Route data from ApsaraMQ for MQTT to ApsaraMQ for RocketMQ |
| Create DTS Source Connector | Console > EventBridge > Streaming Tasks > Create Source Connector | MQ for RocketMQ instance running; DTS subscription task in Normal status; consumer group created | Create a Data Transmission Service source connector |
| Create RocketMQ to Kafka Outflow Task | Console > EventBridge > Message Outflow Tasks > Create Message Outflow Task | ApsaraMQ for RocketMQ instance running; ApsaraMQ for Kafka instance running | Synchronize data from RocketMQ to Kafka |
| Create RocketMQ to SMQ Outflow Task | Console > EventBridge > Message Outflow Tasks > Create Task | ApsaraMQ for RocketMQ instance running; SMQ queue created | Synchronize data from RocketMQ to SMQ |
| Route Messages to Function Compute | Console > EventBridge > Streaming Tasks > Create Sink Task | ApsaraMQ for RocketMQ instance in service; Function Compute activated; EventBridge activated | Route messages to Function Compute service |
| Use Function Compute as Transform | Console > EventBridge > Event Streams > Create Event Stream | EventBridge activated; Function Compute service and function created | Transform event data using Function Compute in event streams |
| Message Inflow | Console > EventBridge > Message Inflow > Create Message Inflow Task | Active EventBridge instance; permissions to create tasks; external source configured | Create message inflow tasks from various sources |

## Step-by-Step Instructions

### Create OSS Sink Connector

**Navigation**: Console > EventBridge > Connectors > Create Connector

**Prerequisites**:
- An OSS bucket created in the OSS console
- Prerequisites documented in the linked guide

1. Navigate to the Connectors page in EventBridge console
   - Element: **Connectors** (link) — left navigation panel

2. Click the 'Create Connector' button
   - Element: **Create Connector** (button) — top-right corner

3. In the Basic Info section, set the connector name and select OSS as the connector type
   - Element: **OSS** (dropdown) — in the Message Outflow Type dropdown

4. In the Destination (OSS) section, set the OSS Bucket and Storage Path parameters
   - Element: **OSS Bucket** (text_input) — in the Destination (OSS) section

5. Set the Time Partition option (e.g., YYYY/MM/dd/HH)
   - Element: **Time Partition** (radio) — in the Destination (OSS) section
   - Notes: Options include: YYYY/MM/dd/HH, YYYY/MM/dd, YYYYMMddHH, YYYYMMdd

6. Set the Batch size and Time window values
   - Element: **Batch size** (number_input) — in the Advanced Settings section
   - Notes: Batch size: 1–128 MiB; Time window: minutes

7. In the panel, configure the following parameters and click Confirm
   - Element: **Confirm** (button) — bottom of the configuration panel

8. Click Enable in the Operations column on the Connectors page
   - Element: **Enable** (button) — in the Operations column of the Connectors table
   - Notes: Connector status must change from Starting to Running

9. Click the source topic in the Source column to view messages
   - Element: **Source** (link) — in the Source column of the Connectors table

10. Configure message content in the Send Message panel and click Confirm
    - Element: **Confirm** (button) — bottom of the Send Message panel

11. Click the destination bucket in the Target column to view the uploaded files
    - Element: **Target** (link) — in the Target column of the Connectors table

12. Navigate to the deepest directory path in the bucket under Objects
    - Element: **Objects** (menu) — left navigation pane

13. Choose Download from the operations menu for the data file
    - Element: **Download** (button) — in the Operations column of the object list

14. Open the downloaded file to view the message content
    - Notes: Messages are separated by line breaks

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| OSS Bucket | text_input | Yes | — | The OSS bucket that you created. |
| Storage Path | text_input | Yes | No path, Time Partition: YYYY/MM/dd/HH, Time Partition: YYYY/MM/dd, Time Partition: YYYYMMddHH, Time Partition: YYYYMMdd | The storage path is {Kafka Instance ID}/{Topic Name} or with time partitioning. |
| Batch size | number_input | No | — | The maximum file size before the data is flushed. Valid values: 1 to 128. Unit: MiB. |
| Time window | number_input | No | — | The maximum time to wait before the data is flushed, regardless of the file size. Unit: minutes. |

### Create Apache Kafka Custom Connector

**Navigation**: Console > EventBridge > Connectors > Create Connector

**Prerequisites**:
- An active Apache Kafka instance with public access or VPC connectivity
- EventBridge service enabled in the target region
- IAM/ RAM permissions for creating connectors and accessing Kafka resources

1. Navigate to the Connectors page in EventBridge console
   - Element: **Connectors** (link) — left navigation panel

2. Click the 'Create Connector' button
   - Element: **Create Connector** (button) — top-right corner

3. Select 'Apache Kafka' as the source type
   - Element: **Apache Kafka** (radio) — Source Type section

4. Enter the Kafka bootstrap server address
   - Element: **Bootstrap Server** (text_input) — Kafka Configuration form
   - Notes: Must be in format: kafka.example.com:9092

5. Configure authentication settings if required
   - Element: **Authentication** (tab) — Kafka Configuration form
   - Notes: Options include None, SASL/PLAIN, SASL/SCRAM

6. Specify the Kafka topic to consume events from
   - Element: **Topic** (text_input) — Kafka Configuration form

7. Set up the connector name and description
   - Element: **Connector Name** (text_input) — Basic Information section

8. Review all settings and click 'Create'
   - Element: **Create** (button) — bottom of the form
   - Notes: Connector creation may take up to 2 minutes

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Connector Name | text_input | Yes | — | Unique identifier for the connector in EventBridge |
| Description | text_input | No | — | Optional description to help identify the connector's purpose |
| Bootstrap Server | text_input | Yes | — | The Kafka broker endpoint (e.g., kafka.example.com:9092) |
| Topic | text_input | Yes | — | The Kafka topic from which to consume events |
| Authentication | dropdown | No | None, SASL/PLAIN, SASL/SCRAM | Authentication method for connecting to Kafka |

### Manage Custom Kafka Connector Tasks

**Navigation**: Console > EventBridge > Event Streams > Create Event Stream

**Prerequisites**:
- EventBridge is activated and RAM user has required permissions
- Object Storage Service (OSS) is activated and a bucket is created
- Serverless App Engine (SAE) is activated
- A virtual private cloud (VPC) and vSwitch are created
- An ApsaraMQ for Kafka instance is purchased and deployed
- Kafka Connect 3.2.3 is installed
- Scala 2.13 is installed
- Java 8 is installed

1. Click Create Event Stream
   - Element: **Create Event Stream** (button) — top-right corner

2. Configure basic information including Event Stream Name and Description
   - Element: **Basic Information** (tab) — top navigation panel

3. Select Apache Kafka Connect from the Event Provider dropdown list
   - Element: **Event Provider** (dropdown) — main content area

4. Configure Kafka Connect Plug-in method (Local Upload or OSS Reference)
   - Element: **Kafka Connect Plug-in** (section) — main content area

5. Select the bucket containing the ZIP file with Kafka Connect configurations
   - Element: **Bucket** (dropdown) — main content area

6. Select the ZIP file from the bucket
   - Element: **File** (dropdown) — main content area

7. Set Message Queue for Apache Kafka Parameters to Source Connect or Sink Connect
   - Element: **Message Queue for Apache Kafka Parameters** (radio) — main content area

8. Select the ApsaraMQ for Kafka instance ID
   - Element: **Message Queue for Apache Kafka Instance** (dropdown) — main content area

9. Select the VPC ID where the ApsaraMQ for Kafka instance is deployed
   - Element: **VPC** (dropdown) — main content area

10. Select the vSwitch ID used by the ApsaraMQ for Kafka instance
    - Element: **vSwitch** (dropdown) — main content area

11. Select the security group associated with the ApsaraMQ for Kafka instance
    - Element: **Security Group** (dropdown) — main content area

12. Choose either Method 1 (select .properties file from ZIP) or Method 2 (configure parameters in console)
    - Element: **Kafka Connect** (section) — main content area
    - Notes: If a ZIP file is uploaded, its configurations will be overwritten by console inputs.

13. Enter connector name, class, task.max, and topics if applicable
    - Element: **name** (text_input) — main content area

14. Configure Worker Type: select 2 Core 4 GIB, set Min Number of Workers to 2, Max Number of Workers to 2, and Horizontal Scaling Threshold to 50%
    - Element: **Worker Type** (dropdown) — main content area
    - Notes: Max number must be equal to or greater than min number.

15. Select Automatically Create Dependencies for Apache Kafka Connector Worker
    - Element: **Automatically Create Dependencies for Apache Kafka Connector Worker** (checkbox) — main content area
    - Notes: Recommended not to change preset values.

16. Select Log Delivery destination: Deliver Data to Log Service or Deliver Data to Message Queue for Apache Kafka
    - Element: **Log Delivery** (radio) — main content area

17. Specify the role on which the connector depends
    - Element: **Role Authorization** (dropdown) — main content area
    - Notes: We recommend attaching AliyunSAEFullAccess policy to the selected role.

18. Click Confirm to finalize creation
    - Element: **Confirm** (button) — bottom-right corner

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Event Stream Name | text_input | Yes | — | The name of the event stream being created. |
| Description | text_input | No | — | Optional description for the event stream. |
| Kafka Connect Plug-in | dropdown | Yes | Local Upload, OSS Reference | Method to import Kafka Connect configuration ZIP file. |
| Bucket | dropdown | Yes | — | The OSS bucket containing the Kafka Connect configuration ZIP file. |
| File | dropdown | Yes | — | The ZIP file containing Kafka Connect configuration. |
| Message Queue for Apache Kafka Parameters | radio | Yes | Source Connect, Sink Connect | Whether data is imported into or exported from ApsaraMQ for Kafka. |
| Message Queue for Apache Kafka Instance | dropdown | Yes | — | The ApsaraMQ for Kafka instance to connect to. |
| VPC | dropdown | Yes | — | The VPC where the ApsaraMQ for Kafka instance is deployed. |
| vSwitch | dropdown | Yes | — | The vSwitch used by the ApsaraMQ for Kafka instance. |
| Security Group | dropdown | Yes | — | The security group associated with the ApsaraMQ for Kafka instance. |
| name | text_input | Yes | — | The connector name, typically without ISO control characters. |
| connector.class | text_input | Yes | — | The class name or alias of the connector, must extend org.apache.kafka.connect.connector.Connector. |
| task.max | number_input | Yes | — | Maximum number of concurrent threads; valid range: 1 to max partitions. |
| topics | text_input | No | — | Comma-separated list of source topics when using Sink Connect. |
| Worker Type | dropdown | Yes | 2 Core 4 GIB | Worker type with auto-scaling support based on CPU utilization. |
| Min. Number of Workers | number_input | Yes | — | Minimum number of workers to scale out; cannot be less than 1. |
| Max. Number of Workers | number_input | Yes | — | Maximum number of workers to scale out; cannot exceed 50. |
| Horizontal Scaling Threshold (%) | number_input | Yes | — | CPU utilization threshold (in %) to trigger auto scaling. |
| Automatically Create Dependencies for Apache Kafka Connector Worker | checkbox | No | — | Automatically creates dependencies for Kafka connector worker. |
| Log Delivery | radio | Yes | Deliver Data to Log Service, Deliver Data to Message Queue for Apache Kafka | Destination for log delivery. |
| Role Authorization | dropdown | Yes | — | The RAM role the connector depends on. |

### Configure Kafka as Event Provider

**Navigation**: Console > EventBridge > Event Streams > Create Event Stream

**Prerequisites**:
- You have activated EventBridge and granted the required permissions
- You have a Message Queue for Apache Kafka instance that is deployed and serving

1. Click on the Create Event Stream button
   - Element: **Create Event Stream** (button) — top-right corner

2. In the wizard, set Source Type to Message Queue for Apache Kafka
   - Element: **Message Queue for Apache Kafka** (radio) — Source step of the wizard

3. Select the region of the source Kafka instance
   - Element: **Region** (dropdown) — Source configuration panel

4. Select the Kafka instance from the list
   - Element: **Kafka Instance** (dropdown) — Source configuration panel

5. Select the topic for message production
   - Element: **Kafka Topic** (dropdown) — Source configuration panel

6. Select a dedicated consumer group for the event source
   - Element: **Kafka Group** (dropdown) — Source configuration panel
   - Notes: Use a dedicated consumer group. Do not share with other services to avoid disrupting existing message delivery.

7. Set the number of consumers for the source instance
   - Element: **Maximum Tasks** (text_input) — Source configuration panel

8. Select the offset from which message consumption begins
   - Element: **Position** (dropdown) — Source configuration panel

9. Select the network type for routing messages
   - Element: **Network Config** (dropdown) — Source configuration panel

10. If using Internet network, select VPC ID, vSwitch ID, and security group
    - Element: **VPC ID** (dropdown) — Source configuration panel
    - Notes: Required only if Network Config is set to Internet

11. Enable batch push and configure batch count and interval
    - Element: **Batch Push** (toggle) — Source configuration panel

12. Set maximum number of messages per batch
    - Element: **Batch Push Count** (text_input) — Source configuration panel

13. Set maximum wait time before function invocation
    - Element: **Batch Push Interval** (text_input) — Source configuration panel

14. Configure event filtering rules, transformation rules, and event sink in subsequent steps
    - Element: **Filter Rules** (text_input) — Wizard steps
    - Notes: For more information about event transformation, see Use Function Compute to clean message data

15. Configure retry policy and dead-letter queue for the event stream
    - Element: **Retry Policy** (text_input) — Task Properties section
    - Notes: For more information, see Retry policies and dead-letter queues

16. Return to the Event Streams page and click Enable for the created event stream
    - Element: **Enable** (button) — Actions column
    - Notes: After enabling, it may take 30 to 60 seconds to start. Monitor progress in the Status column.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Region | dropdown | Yes | China (Beijing), International | Select the region of the source Message Queue for Apache Kafka instance. |
| Kafka Instance | dropdown | Yes | — | Select the source instance that produces Message Queue for Apache Kafka messages. |
| Kafka Topic | dropdown | Yes | — | Select the topic for producing Message Queue for Apache Kafka messages. |
| Kafka Group | dropdown | Yes | — | Select the consumer group for the source instance. Use a dedicated consumer group for the event source. |
| Maximum Tasks | text_input | No | — | Select the number of consumers for the source instance. |
| Position | dropdown | Yes | Latest Offset, Earliest Offset | Select the offset from which message consumption begins. |
| Network Config | dropdown | Yes | Basic Network, Internet | Select the network type over which to route messages. |
| VPC ID | dropdown | No | — | Select the VPC ID. Required only if Network Config is set to Internet. |
| vSwitch ID | dropdown | No | — | Select the vSwitch ID. Required only if Network Config is set to Internet. |
| Security Group | dropdown | No | — | Select a security group. Required only if Network Config is set to Internet. |
| Batch Push | toggle | No | Enable, Disable | Batch push allows you to aggregate multiple events. A push occurs when either the Messages or Interval threshold is reached. |
| Batch Push Count | number_input | No | — | The maximum number of messages to include in a batch for a function invocation. Valid values: 1 to 10,000. |
| Batch Push Interval | number_input | No | — | The maximum time to wait, in seconds, before the function is invoked. Valid values: 0 to 15. A value of 0 means messages are delivered immediately without waiting. |

### Route Events to Function Compute

**Navigation**: Console > EventBridge > Event Streams > Create Event Stream

**Prerequisites**:
- Activate EventBridge and grant permissions to a RAM user
- Create a Function Compute service
- Create a Function Compute function
- Create a Log Project and Logstore
- Set up SLS trigger
- Collect and import logs

1. Log on to the EventBridge console
   - Element: **EventBridge console** (link) — top navigation bar

2. Select a region and click Create Event Stream
   - Element: **Create Event Stream** (button) — top navigation bar

3. Enter a name and description, configure data provider, event filtering, and transformation rules, then click Next
   - Element: **Next** (button) — bottom of the page
   - Notes: The 'Next' button is only enabled after all required fields are filled.

4. Set Service Type to Function Compute and select the target service and function
   - Element: **Function Compute** (dropdown) — Service Type section

5. Select version or alias of the target function
   - Element: **VersionId** (radio) — Version and Alias selection
   - Notes: Options include 'Specified Version' and 'LATEST'.

6. Choose invocation mode: Asynchronous or Synchronous
   - Element: **Asynchronous** (radio) — Invocation Type section
   - Notes: Default is Asynchronous.

7. Select event format: Object format or ObjectList format
   - Element: **Object format** (radio) — Data Format section
   - Notes: Default is ObjectList format.

8. Configure retry policy and dead-letter queue
   - Element: **Retry Policy and Dead-Letter Queue** (text_input) — Task Properties section
   - Notes: Refer to 'Retries and dead-letter queues' for more details.

9. Return to the Event Streams page and enable the event stream
   - Element: **Enable** (button) — Operating column
   - Notes: The event stream starts within 30 to 60 seconds after enabling.

10. Click the function name in the Target column to open the function details page
    - Element: **function name** (link) — Target column
    - Notes: A screenshot shows the function name link.

11. Click the Logs tab and then click View Logs
    - Element: **View Logs** (button) — Logs tab
    - Notes: A screenshot shows the Logs tab interface.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | Enter a unique name for the event stream. |
| Description | text_input | No | — | Provide a brief description of the event stream. |
| Service Type | dropdown | Yes | Function Compute | Select the type of downstream service to receive events. |
| Function Compute Service | dropdown | Yes | — | Select the Function Compute service that will process the events. |
| Function Name | dropdown | Yes | — | Select the specific Function Compute function to invoke. |
| Version or Alias | radio | Yes | Specified Version, LATEST | Choose whether to use a specific version or the latest version of the function. |
| Invocation Type | radio | Yes | Asynchronous, Synchronous | Determine how the function is invoked upon event delivery. |
| Data Format | radio | No | Object format, ObjectList format | Specify how events are delivered to the downstream function. |
| Event Content Transformation | dropdown | No | Complete Event, Partial Event | Select the transformation type for event content. |

### Manage Event Streams

**Navigation**: Console > EventBridge > Event Streams

**Prerequisites**:
- Activate EventBridge
- Grant required permissions

1. Navigate to the Event Streams page
   - Element: **Event Streams** (link) — left navigation panel

2. Click the Create button on the Event Streams page
   - Element: **Create** (button) — top-right corner

3. Select a source type and configure its resources
   - Element: **Event Connector Source** (dropdown) — Task creation step

4. Enter an event pattern in the code editor
   - Element: **Event Pattern Content** (text_input) — Event Pattern Content section

5. Configure event transformation rules
   - Element: **event transformation** (text_input) — Transformation step
   - Notes: For more information, see Use Function Compute to cleanse message data

6. Configure the event target
   - Element: **Event Target** (text_input) — Target configuration step

7. Return to the Event Streams page and click Enable in the Actions column
   - Element: **Enable** (button) — Actions column
   - Notes: After enabling, the stream may take 30 to 60 seconds to start. Monitor progress in the Settle Status column.

8. Find the target event stream and click Disable in the Actions column
   - Element: **Disable** (button) — Actions column
   - Notes: A warning dialog appears: Disabling an event stream may interrupt your services.

9. Confirm the action in the dialog box
   - Element: **Confirm** (button) — dialog box

10. Click Edit in the Actions column for the target event stream
    - Element: **Edit** (button) — Actions column

11. Modify configuration and click Save
    - Element: **Save** (button) — bottom of the form

12. Click Delete in the Actions column for the target event stream
    - Element: **Delete** (button) — Actions column
    - Notes: A warning dialog appears: Once an event stream is deleted, its data cannot be recovered.

13. Confirm the deletion in the dialog box
    - Element: **Confirm** (button) — dialog box

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Event Pattern Content | text_input | No | — | Enter the event pattern to filter incoming events. |
| Retry Policy | dropdown | No | Default, Custom | Configure how many times to retry failed events. |
| Dead-Letter Queue | text_input | No | — | Specify the dead-letter queue to store undeliverable events. |

## FAQ

Q: Where can I find the Event Streams feature in the EventBridge console?
A: Navigate to Console > EventBridge > Event Streams in the left navigation panel. This is the main page for creating, viewing, and managing all your event streams.

Q: What happens if I leave the Batch Push settings at their default values?
A: By default, Batch Push is enabled with a count of 100 messages and an interval of 3 seconds. This means events will be aggregated and sent when either 100 messages accumulate or 3 seconds pass, whichever comes first. This helps optimize throughput and reduce costs.

Q: Can I modify an event stream after it has been created and enabled?
A: Yes, you can edit most configuration aspects of an event stream after creation by clicking the Edit button in the Actions column. However, some core settings like the source type cannot be changed and would require creating a new event stream.

Q: What permissions do I need to create and manage event streams?
A: You need EventBridge activation and RAM permissions that include event stream creation, modification, and management rights. Additionally, you'll need appropriate permissions for any source or target services you're connecting to (like Kafka, Function Compute, etc.).

Q: How long does it take for an event stream to become active after clicking Enable?
A: After clicking Enable, the event stream typically takes 30 to 60 seconds to start processing events. You can monitor the startup progress in the Status column on the Event Streams page.

## Pricing & Billing

### Billing Model
EventBridge event streams are billed per request, with each event processed counting as one request. Different operations may have varying pricing tiers.

### Price Reference
| Tier | Input Price | Output Price |
|------|-------------|--------------|
| Standard | 0.0001 / | 0.0001 / |
| Function Compute | based on Function Compute pricing | based on Function Compute pricing |
| DTS Change Tracking | 0.002 / | 0.002 / |

### Free Tier
- Monthly free requests ranging from 100 to 1,000,000 depending on the specific operation
- Function Compute: 100 monthly
- OSS sink connector: 1000 monthly

### Billing Notes
- Billing occurs based on actual usage; asynchronous tasks are billed upon completion
- Failed tasks may still incur charges in some cases
- Minimum billing units vary by service (e.g., 1 second for SLS, 1 request for most others)
- Custom ApsaraMQ for Kafka connectors are not charged by EventBridge directly, but SAE usage is billed separately