# eb-event-management

Part of **EB**

# EventBridge Event Management Console Guide

## Operations Overview

| Operation | Console Navigation Path | Prerequisites | Description |
|----------|------------------------|---------------|-------------|
| Grant Access to Custom Event Source | Console > EventBridge > Custom Event Sources > Access Control | An existing event bus must be created; A RAM role with appropriate permissions must be available; The custom event source must be registered in EventBridge | Configure permissions for custom event sources by assigning a RAM role |
| Delete Connector | Console > EventBridge > Connectors > Delete Connector | A connector is created | Remove an event connector through the console with confirmation |
| Manage Event Rules and Targets | Console > EventBridge > Events > Manage Events | An active EventBridge event bus must be created; Permissions to create and manage event rules and targets | Create and configure event rules with patterns and multiple targets |
| Edit Connector | Console > EventBridge > Connectors > Edit Connector | A connector is already created | Modify connector parameters and save changes with restart |
| Start Connector | Console > EventBridge > Connectors > Select connector > Click Start | A connector is created | Activate a connector and verify running status |
| Manage Event Target | Console > EventBridge > Event Rules > Manage Targets | An event rule must be created before adding a target; The event bus must be configured and accessible; Required permissions: eventbridge:PutTargets, eventbridge:RemoveTargets | Add, update, or remove targets associated with event rules |
| Query Event by Time Range | Console > EventBridge > Events > Query Events by Time Range | An event bus must be created and active; Events must have been published to the selected event bus; User must have permissions to view events and event details | Search for events within a specific time period with filtering options |
| Manage Event Rules | Console > EventBridge > Event Bus > Event Rules | Activate EventBridge and grant permissions | Create, view, enable, disable, edit, and delete event rules comprehensively |
| Event Transformation | Console > EventBridge > Event Rules > Create Rule | An event bus already created; A target service configured to receive transformed events; Basic understanding of JSON structure and JSONPath syntax | Define input path and template transformations for event payloads |
| Suspend a Connector | Console > EventBridge > Connectors > Suspend Connector | A connector is created | Temporarily disable an event source connector |
| Subscribe to ECS Events | Console > EventBridge > Event Bus > Create Rule | Activate EventBridge and grant required permissions; Create a DingTalk chatbot and record its webhook URL and secret key; Create a service and a function in Function Compute; Create a queue in MNS | Set up event rules to receive notifications from Elastic Compute Service |
| Create HTTP/HTTPS Custom Event Source | Console > EventBridge > Custom Event Sources > Create Custom Event Source | Activate EventBridge and grant the required permissions; Create a custom event bus | Create a custom event source with HTTP/HTTPS trigger configuration |
| Manage Custom Event Buses | Console > EventBridge > Event Buses | Activate EventBridge and grant permissions | Create, view, and delete custom event buses with optional sources, rules, and targets |
| View Metric Monitoring | Console > EventBridge > Custom Event Buses > [Bus Name] > Monitoring | You have activated EventBridge and granted the required permissions; You have created a custom event bus | View detailed metrics for matched events, successful deliveries, and response times |

## Operation Steps

### Grant Access to Custom Event Source

**Navigation**: Console > EventBridge > Custom Event Sources > Access Control

**Prerequisites**:
- An existing event bus must be created
- A RAM role with appropriate permissions must be available
- The custom event source must be registered in EventBridge

1. Navigate to the Custom Event Sources section in the EventBridge console
   - Element: **Custom Event Sources** (link) — left navigation panel

2. Select the custom event source that requires access configuration
   - Element: **Select event source** (button) — main content area
   - Notes: Click on the name of the event source to open its details page.

3. Click on the 'Access Control' tab to configure permissions
   - Element: **Access Control** (tab) — top navigation bar of the event source details page

4. Choose the RAM role to grant access to the event source
   - Element: **Select RAM Role** (dropdown) — Access Control configuration form
   - Notes: Only roles with the required permissions will appear in the list.

5. Click 'Save' to apply the access settings
   - Element: **Save** (button) — bottom of the form
   - Notes: Changes take effect immediately after saving.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| RAM Role | dropdown | Yes | — | Select the RAM role that will be granted permission to publish events to this custom event source. |

### Delete Connector

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

**Prerequisites**:
- A connector is created

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

2. Select the connector you want to delete from the list
   - Element: **Connector name or ID** (checkbox) — main content area

3. Click the Delete button
   - Element: **Delete** (button) — top-right corner

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

5. Wait for the operation to complete
   - Element: **Status update** (text_input) — status column
   - Notes: The connector will be removed from the list once deletion is complete.

6. Verify that the connector no longer appears in the list
   - Element: **Connector list** (table) — main content area

### Manage Event Rules and Targets

**Navigation**: Console > EventBridge > Events > Manage Events

**Prerequisites**:
- An active EventBridge event bus must be created
- Permissions to create and manage event rules and targets

1. Click on 'Create Event Rule' in the top-right corner
   - Element: **Create Event Rule** (button) — top-right corner of the Events page

2. Select the event bus from the dropdown menu
   - Element: **Event Bus** (dropdown) — main content area
   - Notes: Default is 'default' unless a custom bus is configured

3. Define the event pattern using JSON format or visual editor
   - Element: **Event Pattern** (text_input) — main content area
   - Notes: Use the visual editor for simple patterns; switch to JSON for advanced filtering

4. Add a target by clicking 'Add Target' and selecting a service
   - Element: **Add Target** (button) — targets section
   - Notes: Available targets include Lambda, SNS, SQS, and EventBridge itself

5. Configure target-specific settings such as input transformation
   - Element: **Input Transformation** (text_input) — target configuration panel
   - Notes: Optional: Use JSONPath expressions to transform incoming event data

6. Review and click 'Create Rule' to finalize
   - Element: **Create Rule** (button) — bottom of the form
   - Notes: Rule will be activated immediately after creation

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Rule Name | text | Yes | — | A unique name for the event rule to identify it in the console and API |
| Description | text | No | — | Optional description to provide context about the rule's purpose |
| Event Pattern | text | Yes | — | Defines which events trigger this rule. Can be specified via JSON or visual editor |
| Target Type | dropdown | Yes | Lambda Function, Amazon SNS Topic, Amazon SQS Queue, Another EventBridge Event Bus | Specifies the destination service that receives the event |
| Input Transformer | checkbox | No | — | Enable to modify the event payload before sending to the target |

### Edit Connector

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

**Prerequisites**:
- A connector is already created

1. Navigate to the Edit Connector page
   - Element: **Edit Connector** (link) — main content area

2. Modify the connector parameters
   - Element: ** ** (text_input) — main content area

3. Click Save and Start to apply changes and restart the connector
   - Element: **Save and Start** (button) — bottom of the form

### Start Connector

**Navigation**: Console > EventBridge > Connectors > Select connector > Click Start

**Prerequisites**:
- A connector is created

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

2. Select the connector you want to start from the list
   - Element: **Connector name or ID** (link) — main content area

3. Click the Start button
   - Element: **Start** (button) — top-right corner

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

5. Wait for the connector status to change to 'Running'
   - Element: **Status column** (text_input) — main content area
   - Notes: The status may take a few seconds to update.

6. Verify that the connector is active and processing events
   - Element: **Event logs or metrics** (tab) — main content area

### Manage Event Target

**Navigation**: Console > EventBridge > Event Rules > Manage Targets

**Prerequisites**:
- An event rule must be created before adding a target
- The event bus must be configured and accessible
- Required permissions: eventbridge:PutTargets, eventbridge:RemoveTargets

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

2. Select an existing event rule from the list
   - Element: **Select Rule** (button) — main content area
   - Notes: Clicking this opens the rule details view.

3. Click the 'Targets' tab to view or manage targets
   - Element: **Targets** (tab) — top navigation of rule details

4. Click 'Add Target' to create a new event target
   - Element: **Add Target** (button) — top-right corner of Targets tab

5. Select a target type from the dropdown menu
   - Element: **Target Type** (dropdown) — form fields in Add Target dialog
   - Notes: Available options include Lambda function, SQS queue, SNS topic, and EventBridge event bus.

6. Configure the target settings based on the selected type
   - Element: **Configure Target** (text_input) — form fields in Add Target dialog
   - Notes: For example, specify the ARN of the Lambda function or SQS queue.

7. Click 'Confirm' to save the new target
   - Element: **Confirm** (button) — bottom of dialog

8. To update or remove a target, click the edit or delete icon next to the target entry
   - Element: **Edit** (button) — Actions column of target list
   - Notes: Editing allows changing target configuration; deletion removes the target from the rule.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Target Type | dropdown | Yes | Lambda Function, Amazon SQS Queue, Amazon SNS Topic, EventBridge Event Bus, Kinesis Data Stream | Specifies the service that will receive the event when the rule is triggered |
| Target ARN | text_input | Yes | — | The Amazon Resource Name (ARN) of the target resource. Must be valid and accessible |
| Input Template | text_input | No | — | Optional JSON template to transform the event data before sending it to the target |
| Retry Policy | dropdown | No | Default retry policy, Custom retry policy, No retry | Controls how many times EventBridge retries delivering the event if the target is unreachable |

### Query Event by Time Range

**Navigation**: Console > EventBridge > Events > Query Events by Time Range

**Prerequisites**:
- An event bus must be created and active
- Events must have been published to the selected event bus
- User must have permissions to view events and event details

1. Navigate to the EventBridge console and select the 'Query by Time Range' tab
   - Element: **Query by Time Range** (tab) — top navigation panel

2. Configure the time range, event bus, event source, event type, and rule filters
   - Element: **Time Range** (dropdown) — filter section
   - Notes: You can also specify a custom start and end time.

3. Click the 'Query' button to execute the search
   - Element: **Query** (button) — bottom of the filter form

4. Locate the target event in the results list and click 'Trace' in the Actions column
   - Element: **Trace** (link) — Actions column
   - Notes: This opens the event trace page showing send and filter details.

5. View event details on the Trace or Detail page
   - Element: **Event Detail** (link) — main content area
   - Notes: The response includes JSON structure with fields like id, source, type, data, and timestamps.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Time Range | dropdown | Yes | Last 1 hour, Last 6 hours, Last 24 hours, Last 7 days, Custom | Specifies the time window for event queries. Custom allows manual start/end time input |
| Event Bus | dropdown | Yes | — | Selects the event bus from which events are retrieved |
| Event Source | dropdown | No | — | Filters events by their originating service or application |
| Event Type | dropdown | No | — | Filters events by type, such as 'Created', 'Updated', or 'Deleted' |
| Rule | dropdown | No | — | Applies filtering based on a specific EventBridge rule that processes the event |

### Manage Event Rules

**Navigation**: Console > EventBridge > Event Bus > Event Rules

**Prerequisites**:
- Activate EventBridge and grant permissions

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

2. Click Event Bus in the left-side navigation pane
   - Element: **Event Bus** (menu) — left-side navigation panel

3. Select a region in the top navigation bar
   - Element: **region dropdown** (dropdown) — top navigation bar

4. Click the name of the target event bus
   - Element: **event bus name** (link) — Event Bus page

5. Click Event Rules in the left-side navigation pane
   - Element: **Event Rules** (menu) — left-side navigation panel

6. Click Create Rule on the Event Rules page
   - Element: **Create Rule** (button) — top-right corner

7. Enter a name and optional description in the Basic step
   - Element: **name text box** (text_input) — Basic step

8. Configure event source and event type or custom event source and event pattern in the Filter step
   - Element: **event source list** (dropdown) — Filter step
   - Notes: Events from Alibaba Cloud services cannot be published to custom event buses.

9. Configure one or more event targets in the Targets step
   - Element: **Add Target** (button) — Targets step
   - Notes: You can add up to five event targets. The target service and the event rule must be in the same region.

10. Click View Rule in the Operations column
    - Element: **View Rule** (button) — Operations column
    - Notes: The Rule Detail page shows basic information, event pattern, and event targets.

11. Choose Disable from the More menu in the Operations column
    - Element: **More** (menu) — Operations column
    - Notes: Disabling an event rule may cause some services to become unavailable.

12. Click OK in the confirmation dialog box
    - Element: **OK** (button) — confirmation dialog

13. Enter verification code and click Confirm in the risk validation dialog
    - Element: **verification code text box** (text_input) — risk validation dialog

14. Choose Enable from the More menu in the Operations column
    - Element: **More** (menu) — Operations column

15. Click Edit Targets in the Operations column
    - Element: **Edit Targets** (button) — Operations column

16. Modify event target configurations and click Confirm
    - Element: **Confirm** (button) — Edit Rule page

17. Click Edit Pattern in the Operations column
    - Element: **Edit Pattern** (button) — Operations column

18. Modify event pattern and click Confirm
    - Element: **Confirm** (button) — Edit Rule page

19. Choose Delete from the More menu in the Operations column
    - Element: **More** (menu) — Operations column
    - Notes: A deleted event rule cannot be recovered.

20. Click OK in the confirmation dialog box
    - Element: **OK** (button) — confirmation dialog

21. Enter verification code and click Confirm in the risk validation dialog
    - Element: **verification code text box** (text_input) — risk validation dialog

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text | Yes | — | Enter a name for the rule |
| Description | text | No | — | Enter an optional description for the rule |
| Event Source | dropdown | Yes | Alibaba Cloud Service Event Sources, Custom Event Source | Select an event source for the rule |
| Event Type | dropdown | Yes | — | Select an event type from the selected event source |
| Event Pattern | text | Yes | — | Enter an event pattern in JSON format for custom event sources |
| Target Service | dropdown | Yes | Function Compute, ApsaraMQ for RocketMQ, ApsaraMQ for RabbitMQ, Message Service (MNS), EventBridge, HTTP gateway, HTTPS gateway, Short Message Service, Direct Mail, DingTalk, ApsaraDB RDS for MySQL, self-managed MySQL database | Select a service to receive events |
| Transformation Method | dropdown | No | — | Select an event transformation method if needed |

### Event Transformation

**Navigation**: Console > EventBridge > Event Rules > Create Rule

**Prerequisites**:
- An event bus already created
- A target service configured to receive transformed events
- Basic understanding of JSON structure and JSONPath syntax

1. Click the 'Add transformation' button in the rule configuration panel
   - Element: **Add transformation** (button) — rule configuration section

2. Select a transformation method from the dropdown menu
   - Element: **Transformation method** (dropdown) — transformation settings panel
   - Notes: Available options: Complete Event, Partial Event, Constant, Template

3. Enter the JSONPath expression or static value based on selected method
   - Element: **Configuration input field** (text_input) — configuration area below method selection
   - Notes: For Template, enter a JSON object for variables and a string/JSON template

4. Use the 'Preview' button to test the transformation result
   - Element: **Preview** (button) — bottom of transformation panel
   - Notes: Shows the output based on the sample event provided

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Transformation method | dropdown | Yes | Complete Event, Partial Event, Constant, Template | Specifies how the event payload is transformed before delivery to the target |
| Configuration | text | Yes | — | Contains the JSONPath expression (for Partial Event), fixed string (for Constant), or variable/template definition (for Template) |

### Suspend a Connector

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

**Prerequisites**:
- A connector is created

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

2. Locate the target connector in the list
   - Element: ** ** (table) — main content area

3. Click the Actions menu for the connector
   - Element: **Actions** (dropdown) — rightmost column of the table

4. Select 'Suspend' from the dropdown menu
   - Element: **Suspend** (link) — Actions dropdown

5. Confirm the suspension in the dialog box
   - Element: **Confirm** (button) — bottom of dialog

6. Wait for the status to update to 'Suspended'
   - Element: ** ** (status badge) — status column

### Subscribe to ECS Events

**Navigation**: Console > EventBridge > Event Bus > Create Rule

**Prerequisites**:
- Activate EventBridge and grant required permissions
- Create a DingTalk chatbot and record its webhook URL and secret key
- Create a service and a function in Function Compute
- Create a queue in MNS

1. Click the default event bus
   - Element: **default** (link) — on the EventBridge page

2. Navigate to the event rules section and create a new rule
   - Element: **Create Rule** (button) — in the left navigation bar

3. Enter a name and description for the rule
   - Element: **Configure Basic Information tab** (tab) — in the Create Rule panel

4. Select the event source and event types
   - Element: **acs.ecs** (dropdown) — in the Filter tab
   - Notes: From the event source dropdown, select acs.ecs; from the event type dropdown, select one or more event types.

5. Configure the target delivery scenario
   - Element: **Targets tab** (tab) — in the Create Rule panel
   - Notes: Choose a target service type such as MNS, DingTalk, HTTP, Function Compute, or EventBridge Event Bus.

6. Set up retry policy and dead-letter queue
   - Element: **Retry policy and dead-letter queue settings** (section) — below the Targets tab
   - Notes: Configure retry strategy (BACKOFF_RETRY or EXPONENTIAL_DECAY_RETRY) and specify a dead-letter queue if needed.

7. Trigger an ECS instance state change to generate an event
   - Element: **Status** (menu) — in the top navigation bar
   - Notes: Change the state of an ECS instance via the console to trigger the event.

8. View delivery results using the event ID
   - Element: **Trace** (button) — in the Actions column for the event
   - Notes: Click Trace to view delivery details including success/failure status and latency.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Rule Name | text | Yes | — | A unique name for the event rule |
| Description | text | No | — | Optional description for the rule |
| Event Source | dropdown | Yes | acs.ecs | The cloud service that generates the events |
| Event Type | dropdown | No | ecs:Instance:StateChange, ecs:Instance:Creation, ecs:Instance:Deletion | The specific type of ECS event to subscribe to |
| Target Service Type | dropdown | Yes | MNS, DingTalk, HTTP, Function Compute, EventBridge Event Bus | The destination where the event will be delivered |
| Queue Name | dropdown | Yes | — | The existing MNS queue to which events will be delivered |
| Webhook URL | text | Yes | — | The URL of the DingTalk chatbot webhook |
| Secret Key | text | Yes | — | The secret key for authenticating the DingTalk chatbot |
| URL | text | Yes | — | The endpoint URL that receives the event payload |
| Body Format | dropdown | Yes | Complete Event, Partial Event, Fixed Value, Template | The format of the event payload sent to the target |
| Network Access | radio | Yes | Public Network, Private Network | Whether the target is accessible over the public internet or within a VPC |
| Service Name | text | Yes | — | The name of the Function Compute service to invoke |
| Function Name | text | Yes | — | The name of the Function Compute function to invoke |
| Invocation Type | radio | Yes | Synchronous, Asynchronous | Whether the function should return immediately or wait for completion |
| Region | dropdown | Yes | — | The region where the target event bus is located |
| Target Event Bus | text | Yes | — | The name of the target event bus for cross-account or cross-region delivery |
| Retry Strategy | radio | Yes | BACKOFF_RETRY, EXPONENTIAL_DECAY_RETRY | The method used to retry failed deliveries |
| Fault Tolerance | radio | Yes | ALL, NONE | Whether to allow out-of-order processing during failures |

### Create HTTP/HTTPS Custom Event Source

**Navigation**: Console > EventBridge > Custom Event Sources > Create Custom Event Source

**Prerequisites**:
- Activate EventBridge and grant the required permissions
- Create a custom event bus

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

2. Enter a name and description, select HTTP/HTTPS as the event source type, configure parameters, and click OK
   - Element: **OK** (button) — bottom of the panel

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | The name of the custom event source |
| Description | text_input | No | — | A brief description of the custom event source |
| Event Source Type | dropdown | Yes | HTTP and HTTPS, HTTP, HTTPS | Select the protocol(s) that the event source will accept |
| Request Methods | checkbox | No | GET, POST, PUT, DELETE, HEAD, PATCH | Select one or more HTTP request methods to allow |
| Security Configuration | radio | Yes | None, CIDR Block, Security Domain Name | Choose the security setting for incoming requests |
| CIDR Block | text_input | No | — | Enter valid IP addresses or CIDR blocks. Required only if Security Configuration is set to CIDR Block. Up to five entries allowed |
| Security Domain Name | text_input | No | — | Enter secure domain names. Required only if Security Configuration is set to Security Domain Name. Up to five entries allowed |

### Manage Custom Event Buses

**Navigation**: Console > EventBridge > Event Buses

**Prerequisites**:
- Activate EventBridge and grant permissions

1. Click the Create button in the Custom Event Buses section
   - Element: **Create** (button) — Custom Event Buses section

2. Enter the event bus name and description, then click Next
   - Element: **Next** (button) — Event Bus (Required) step

3. Optionally enter an event source name and description, select provider and resource, then click Next
   - Element: **Next** (button) — Event Source step
   - Notes: You can skip this step to add a custom event source later.

4. Optionally define an event pattern in the code editor, then click Next
   - Element: **Next** (button) — Rule panel
   - Notes: You can skip this step to create the bus without a rule or targets.

5. Optionally configure event targets, then click Create
   - Element: **Create** (button) — Target panel
   - Notes: You can skip this step to create the bus without targets.

6. Click Details in the Actions column for the desired event bus
   - Element: **Details** (link) — Actions column
   - Notes: The Details page displays basic and endpoint information.

7. Click Delete in the Actions column for the event bus to delete
   - Element: **Delete** (button) — Actions column

8. Click OK in the Note dialog box to confirm deletion
   - Element: **OK** (button) — Note dialog box

9. Optionally enter verification code and click OK in the Risk Validation dialog box
   - Element: **OK** (button) — Risk Validation dialog box
   - Notes: A verification code is sent via SMS; cannot be recovered after deletion.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Event Bus (Required) | text | Yes | — | Enter the name and description of the custom event bus |
| Event Source | text | No | — | Optionally enter a custom event source name and description, and select an event provider and its resource |
| Rule Name | text | No | — | Optionally enter a rule name and description, and define an event pattern in the code editor |
| Target | text | No | — | Optionally configure one or more event targets for the event bus |

### View Metric Monitoring

**Navigation**: Console > EventBridge > Custom Event Buses > [Bus Name] > Monitoring

**Prerequisites**:
- You have activated EventBridge and granted the required permissions
- You have created a custom event bus

1. Click the Monitoring option in the left-side navigation pane
   - Element: **Monitoring** (link) — left-side navigation pane

2. Review the displayed metrics on the Monitoring page
   - Element: **Monitoring** (tab) — main content area
   - Notes: The console displays data for the last hour by default. You can select a different time range at the top of the page. If multiple event rules exist, you can filter by a specific rule using the drop-down list. Click the zoom icon on any chart to expand its view.

## FAQ

Q: Where do I find the event tracing feature to debug delivery issues?
A: Navigate to Console > EventBridge > Event Tracing. You can query events by ID or time range, then click "Trace" in the Actions column to view delivery details and processing paths.

Q: What happens if I leave the event pattern field empty when creating a rule?
A: An empty event pattern acts as a catch-all that matches all events published to the selected event bus. This is useful for broad event capture but may increase costs due to higher event volume processing.

Q: Can I modify event targets after creating a rule?
A: Yes. Go to Console > EventBridge > Event Bus > Event Rules, find your rule, and click "Edit Targets" in the Operations column to add, modify, or remove targets without recreating the entire rule.

Q: What permissions do I need to manage custom event sources?
A: You need RAM permissions including eventbridge:CreateEventSource, eventbridge:UpdateEventSource, eventbridge:DeleteEventSource, and eventbridge:ListEventSources. Additionally, you need permissions to manage the underlying resources that generate events.

Q: How do I verify that my HTTP/HTTPS custom event source is working?
A: After creating the source, use the provided webhook URL to send a test event. Then navigate to Console > EventBridge > Event Tracing and query by time range to see if your event appears in the results list.

## Pricing & Billing

### Billing Model
EventBridge uses a pay-as-you-go billing model based on actual usage. Charges apply per request for event publishing, rule matching, and event delivery operations.

### Price Reference
| Tier | Input Price | Output Price |
|------|-------------|--------------|
| standard | 0.0001 / | 0.0001 / |
| custom_event_source | 0.0001 / | — |
| custom event bus | 0.0001 / | — |

### Free Tier
- Monthly 10,000 free calls for custom event source access
- Monthly 100,000 free event processing calls
- Monthly 1,000 free connector calls
- Monthly 1,000 free event queries
- Monthly 10,000 free event conversions
- Monthly 100 free custom event bus requests

### Billing Notes
- Access control configuration itself does not incur charges, but each event publication is billed per request
- Event delivery failures are not billed; asynchronous tasks are charged based on actual completion count
- Query operations are billed per request regardless of result quantity
- Deleted event buses and rules cannot be recovered
- Suspension of connectors does not incur additional charges