PAI workspace event notification configuration

1.1 Activate EventBridge

On the Event Notification Configuration tab, click Activate for Free to go to the EventBridge activation page. For more information, see Activate EventBridge.

After activation, PAI automatically creates a custom event bus for each PAI workspace. The event bus is named pai-system-${workspace_name}. You can go to the EventBridge console, switch to the target region, and view and manage your custom event buses.

1.2 Grant PAI access to cloud resources

Click Authorize Now. The system automatically creates the AliyunServiceRoleForPAIWorkspace service-linked role. This role authorizes PAI to access your cloud resources. For more information about this role, see Appendix: PAI workspace service-linked role.

In the One-Click Authorization dialog box, click Authorize.

1.3 (Optional) RAM user permissions for event configuration

If you use a RAM user for configuration, you must grant that user permissions to manage EventBridge.

Create a custom policy and attach it to the RAM user. The policy content is as follows:

{
  "Statement": [{
    "Effect": "Allow",
    "Action": [
      "eventbridge:CreateEventBus",
      "eventbridge:GetEventBus",
      "eventbridge:DeleteEventBus",
      "eventbridge:ListEventBuses",
      "eventbridge:CreateRule",
      "eventbridge:GetRule",
      "eventbridge:UpdateRule",
      "eventbridge:EnableRule",
      "eventbridge:DisableRule",
      "eventbridge:DeleteRule",
      "eventbridge:ListRules",
      "eventbridge:PutEvents",
      "eventbridge:UpdateTargets",
      "eventbridge:DeleteTargets",
      "eventbridge:ListTargets"
    ],
    "Resource": "acs:eventbridge:*:*:eventbus/*"
  }],
  "Version": "1"
}

2.1 Configure event type

Select the event source and the specific event types that you want to monitor.

• Flow task: Monitor the status of Designer Flow tasks. Event types include:

  • Task failure.

  • Task completion (successful or failed).

• DLC job: Monitor the lifecycle events of a DLC job. You can select multiple event types. Event types include:

  • Job progress (for example, Queued, Bidding Started, Running, or Failed).

  • Automatic fault tolerance.

  • Job timeout (a timeout rule must be configured in scheduling configuration).

  • Other events (for example, job preempted or job manually stopped).

• Model: Monitor the status changes of a model version in AI Asset Management. Event types include:

  • Model version approved for deployment (status changes from Pending to Approved).

  • Model version status change (approved or rejected for deployment).

• DSW instance: Monitor the status changes of a DSW instance and its saved images. You can select multiple event types. Event types include:

  • Instance status change (for example, Creating or Instance Failed).

  • Image saving (for example, Saving Image, Image Saved Successfully, or Image Save Failed).

  • Instance shutdown (for example, Instance Stopped or Stopping).

2.2 Configure event targets

Configure how and where to deliver notifications when an event occurs.

• DingTalk notification: Configure the webhook and the signing key. For more information, see Appendix: Obtain the webhook and signing key. After configuration, you can click Test Connectivity to verify the setup.

• WeCom notification: Configure the webhook URL for WeCom messages.

• Lark notification: Configure the webhook URL for a custom Lark bot.

• HTTP/HTTPS: Automatically calls a specified URL when the status of a model version changes. This target applies only to Model event types, and your receiving API must parse the request according to the specified template.

• Voice call, text message, and email: Notifies specified contacts. This method is not applicable to Model event types. If no contacts are available for selection, you must first complete the message receiving settings.