Send SMQ delivery events to DingTalk via EventBridge-Cloud Config(CloudConfig)-阿里云帮助中心

Prerequisites

EventBridge is activated. Activate EventBridge and grant permissions.
SMQ is activated. Activate SMQ and authorize RAM users to access SMQ.

Important
SMQ topics and queues incur fees. Billing.

Overview

Cloud Config delivers events to Simple Log Service, Object Storage Service (OSS), or SMQ. With EventBridge, you can route these events to additional channels such as DingTalk, Message Queue, Function Compute, Short Message Service, or Alibaba Mail. This topic uses a resource non-compliance event as an example: an EventBridge event flow converts the non-compliance detection into an event and sends it to DingTalk in a specified format.

Step 1: Create an SMQ topic and queue

Create an SMQ topic.

Create a topic.
Create an SMQ queue.

Create a queue.
Subscribe the queue to the SMQ topic so that messages sent to the topic are pushed to the queue.

Create and use subscriptions.

Note

Skip this step if you already have an SMQ topic and queue.

Step 2: Configure event delivery to SMQ

Create a Cloud Config rule.

Create a rule based on a managed rule or Create a custom rule based on Function Compute.
Configure event delivery to SMQ.

Deliver resource data to an MNS topic.

Note

Skip this step if you already have a Cloud Config rule with SMQ delivery configured.

Step 3: Create an EventBridge event bus and configure event delivery

Log on to the EventBridge console.
In the left navigation pane, click EventBridge.
In the top navigation pane, select a region.
On the input tab, click Quickly Create.
In the Create Custom Event Bus panel, configure the parameters.
1. On the Event Bus page, enter a name and description for the custom event bus, and then click Next.
2. On the Event Source page, configure the following parameters and click Next.
  1. Specify Event Source Name. In this example, enter noncompliant.event.
  2. From the Event Provider drop-down list, select Simple Message Queue (formerly MNS).
  3. Select a QueueName.
  4. Select Enable Base64 Decoding.
3. On the Rules page, configure the following parameters and click Next.
  1. For Rule Name, enter a name such as noncompliant-resource-rule.
  2. Configure the pattern content to filter events.
    
    The following configuration delivers only events with the source noncompliant.event to the event target. Event patterns.
```
{
    "source": [
        "noncompliant.event"
    ]
}
```
4. On the Target page, configure the following parameters and click Create.
  1. From the Service type drop-down list, select acs.dingtalk.
  2. Configure the Webhook address and Secret key for the DingTalk group.
    
    To obtain the webhook address, see Add a custom chatbot.
  3. Configure the Pushed Content parameter.
    
    The following template extracts the resource Alibaba Cloud Resource Name (ARN) and rule name from non-compliance events and pushes them to DingTalk. Event transformation.
```
/**Variables**/
{
  "resourceArn": "$.data.messageBody.evaluationResultIdentifier.evaluationResultQualifier.resourceArn",
  "configRuleName": "$.data.messageBody.evaluationResultIdentifier.evaluationResultQualifier.configRuleName"
}
```
```
/**Template**/
{
  "msgtype": "text", 
  "text": {
      "content": "Resource non-compliance notification: Resource: ${resourceArn}. Rule name: ${configRuleName}"
  }
}
```

Step 4: Verify the result

Log on to the Cloud Config console.
In the left-side navigation pane, choose Compliance & Audit > Rules.
On the Rules page, find your target rule, click the icon in the Actions column, and then click Re-evaluate.
Go to the DingTalk group configured in Step 3 and check for chatbot notifications.

If the group shows resource non-compliance notifications, the configuration is successful.

FAQ

Can I use the SMQ topic configured for event delivery as the event bus event source?

No. EventBridge event buses support only SMQ queues as event sources. Configure a queue for the SMQ topic and use that queue as the event source.

Why does DingTalk fail to receive notifications after I configure an EventBridge event flow and manually run evaluation?

If no non-compliant resources exist, notifications are not sent. Verify that non-compliant resources exist in the Cloud Config console:
1. Log on to the Cloud Config console.
2. In the left-side navigation pane, choose Compliance & Audit > Rules.
  
  Check the rule evaluation results for non-compliant resources.
Verify event delivery in the EventBridge console:
1. Log on to the EventBridge console.
2. In the left navigation pane, click EventBridge.
3. On the EventBridge page, find your event bus and click Event tracking in the Actions column.
  
  Query events by time range to verify that data exists in the event source.
4. Find the target event and click Event trace in the Actions column.
  
  In the Event Trace dialog box, verify that the event was delivered.

What do I do if EventBridge event delivery fails?

If the error message [500]java.lang.RuntimeExceptionjava.lang.RuntimeExceptionjava.lang.RuntimeException is missing parameter JSON appears, perform the following steps:

Ensure that key-value pairs in the $.data object do not contain unescaped quotation marks. Unescaped quotes truncate the JSON string after variable substitution. Use the built-in jsonEscape tool in your rule template to handle variables that may contain quotes. In the following example, jsonEscape escapes the configRuleName variable:
```
/**Variables**/
{
  "resourceArn": "$.data.messageBody.evaluationResultIdentifier.evaluationResultQualifier.resourceArn",
  "configRuleName": "$.data.messageBody.evaluationResultIdentifier.evaluationResultQualifier.configRuleName"
}
```
```
/**Template**/
{
  "msgtype": "text", 
  "text": {
      "content": "Resource non-compliance notification: Resource: ${resourceArn}. Rule name: ${jsonEscape(configRuleName)}"
  }
}
```
If the error message [500]java.lang.RuntimeExceptionjava.lang.RuntimeExceptionjava.lang.RuntimeExceptionsendtoofast,exceed20timesperminute appears:

DingTalk rate-limits custom chatbots to 20 messages per minute per group. Exceeding this limit triggers a 10-minute throttle. To send high-volume messages such as monitoring alerts, consolidate them into a single Markdown message. Add a custom chatbot.