---
Title: Manage targets
URL Source: https://company-skill.com/p/eb/eb-manage-targets
Language: en
Description: You want to register or configure event sources (like RabbitMQ, Kafka, or HTTP endpoints), define where events go (targets like Function Compute or DingTalk), and inspect delivered events. This…
---

# Manage targets

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

## What You Want to Do

You want to register or configure event sources (like RabbitMQ, Kafka, or HTTP endpoints), define where events go (targets like Function Compute or DingTalk), and inspect delivered events. This includes setting up retry policies, dead-letter queues, input transformations, and viewing delivery traces.

**Typical User Questions**:
- How to list all event sources?
- Can I grant permissions to a custom event source?
- Is there a way to edit connectors in console?

## Decision Tree

Pick the best path for your situation:

- **If** you need to call `CreateEventSource` programmatically or configure `BACKOFF_RETRY` policies via code → Use API (go to *eb/eb-event-management*)
- **If** you want to interactively manage `Connectors`, use the visual `Event Rules` editor, or click **Trace** after using **Query by Time Range** → Use (go to *eb/eb-event-management*)
- **If** you need to **Add Target** for more than 5 services per rule or require millisecond-precision event queries → Use API (go to *eb/eb-event-management*)
- **Otherwise (default)** → Use — it’s simpler for one-off debugging, visual rule building, and quick inspection of recent events via **Monitoring** and **Trace**.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| API | medium | Yes | Yes | 100 | `eb/api/eb-event-management` |
| // | low | No | No | 5 API 100 | `eb/guide/eb-event-management` |

## Path Details

### Path 1: API 

**Brief Description**: EventBridge REST API a synchronous HTTP service that lets you programmatically call `CreateEventSource`, configure event targets with `BACKOFF_RETRY` retry strategies and dead-letter queues, publish CloudEvents 1.0 events, and query events by ID or time range. It supports precise control over event routing logic and integration into automated systems.

**Key technical facts**:
- Billing: API 0.0001 /
- Auth method: AccessKey Authorization acs <AccessKeyId>:<Signature> HMAC-SHA1 
- Regions available: cn-hangzhou, cn-shanghai, cn-beijing
- Prerequisites: ALIBABA_CLOUD_ACCESS_KEY_ID ALIBABA_CLOUD_ACCESS_KEY_SECRET RAM 

**When to Use**:
- CloudEvents 1.0 

### Path 2: Console / Dashboard
**Best For**: //

**Brief Description**: The EventBridge provides a GUI to manage `Connectors`, create `Event Rules` with a visual pattern editor, configure targets via form-based **Add Target**, apply **Input Transformation**, and use **Query by Time Range** to inspect events. You can click **Trace** to see delivery status and leverage built-in **Monitoring** dashboards.

**Key technical facts**:
- Billing: 0.0001 / 1000 
- Auth method: SSO 
- Prerequisites: EventBridge RAM eventbridge:PutTargets

- 24 **Trace** 
- DingTalk Function Compute Webhook URL

**Known Limitations**:
- 5 API 100 
- HTTP/HTTPS CIDR **Security Domain Name** 5 

## FAQ

Q: Which path should I start with?
A: Start with the Console if you’re exploring, debugging, or managing fewer than 5 targets per rule. Switch to the API if you need automation, >5 targets, or precise event querying.

Q: What if I need to configure 10 event targets for a single rule but used the Console?
A: You’ll hit the hard limit of 5 targets per rule in the Console — you must use the API path, which supports up to 100 targets per rule.

Q: What if I require millisecond-accurate event queries (e.g., between 14:30:00.123 and 14:30:05.456) but chose the Console?
A: The Console only offers coarse **Query by Time Range** presets (e.g., “last 1 hour”) — you won’t be able to specify exact timestamps and may miss relevant events.

Q: Can I use **Input Transformation** in both paths?
A: Yes, but in the Console it’s done via a visual form under **Add Target**, while in the API you must provide JSONPath or template strings directly.

Q: Do both paths support **Custom Event Sources**?
A: Yes — but the API uses `CreateEventSource` with RAM roles, while the Console guides you through form-based creation and enforces **Security Domain Name** or CIDR restrictions.

Q: Will I be charged for failed API calls when managing targets?
A: Generally no — failed requests are not billed except for certain configuration operations (per the API billing model).

Q: Can I recover a deleted event bus in the Console?
A: No — both paths share this limitation: deleted event buses and rules cannot be restored, so use caution in either interface.

## Related queries

manage event sources, manage event targets, add custom event source, list all event sources, grant permissions to event source, manage eventbus targets, query events, edit connectors in console, event source management, event target configuration, how to add event target, can I manage connectors, ev

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