本文属于机器翻译版本。若本译文内容与英语原文存在差异,则一律以英文原文为准。
亚马逊为亚马逊 EventBridge 举办的活动 EBS
EventBridge 对于对卷和快照执行的操作,Amazon 会向亚马逊EBS发送事件。借 EventBridge助,您可以建立触发编程操作以响应这些事件的规则。例如,您可以创建一个规则,在启用快照以快速恢复快照时向您的电子邮件发送通知。
中的事件以 EventBridge JSON对象的形式表示。事件特有的字段包含在JSON对象的 “详细信息” 部分中。“事件”字段包含事件名称。“结果”字段包含触发事件的操作的已完成状态。有关更多信息,请参阅《亚马逊 EventBridge 用户指南》中的亚马逊 EventBridge 事件模式。
有关更多信息,请参阅什么是亚马逊 EventBridge? 在《亚马逊 EventBridge 用户指南》中。
EBS成交量事件
当发生以下卷事件 EventBridge 时,Amazon 会EBS向发送事件。
创建音量 (createVolume)
创建卷的操作完成后,该createVolume
事件就会发送到您的 AWS 账户。不过,不会保存、记录或存档该事件。此事件的结果可能是 available
或 failed
。如果提供的内容无效 AWS KMS key ,则创建将失败,如以下示例所示。
事件数据
下面的列表是成功createVolume
事件所发射的JSON对象EBS的示例。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
:012345678901
:volume/vol-01234567
"
],
"detail": {
"result": "available",
"cause": "",
"event": "createVolume",
"request-id": "01234567
-0123
-0123
-0123
-0123456789ab
"
}
}
下面的列表是失败createVolume
事件发生EBS后发射的JSON对象的示例。失败的原因是KMS密钥被禁用。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-0123456789ab
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "sa-east-1
",
"resources": [
"arn:aws:ec2:sa-east-1
:0123456789ab
:volume/vol-01234567
",
],
"detail": {
"event": "createVolume",
"result": "failed",
"cause": "arn:aws:kms:sa-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
is disabled.",
"request-id": "01234567
-0123
-0123
-0123
-0123456789ab
",
}
}
以下是失败createVolume
事件发生EBS后发射的JSON对象的示例。失败的原因是KMS密钥待导入。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-0123456789ab
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "sa-east-1
",
"resources": [
"arn:aws:ec2:sa-east-1
:0123456789ab
:volume/vol-01234567
",
],
"detail": {
"event": "createVolume",
"result": "failed",
"cause": "arn:aws:kms:sa-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
is pending import.",
"request-id": "01234567
-0123
-0123
-0123
-0123456789ab
",
}
}
删除音量 (deleteVolume)
删除卷的操作完成后,该deleteVolume
事件就会发送到您的 AWS 账户。不过,不会保存、记录或存档该事件。此事件具有 deleted
结果。如果删除操作未完成,绝不会发送此事件。
事件数据
下面的列表是成功deleteVolume
事件所发射的JSON对象EBS的示例。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
:012345678901
:volume/vol-01234567
"
],
"detail": {
"result": "deleted",
"cause": "",
"event": "deleteVolume",
"request-id": "01234567
-0123
-0123
-0123
-0123456789ab
"
}
}
连接或重新连接音量 (attachVolume,reattachVolume)
如果卷无法附加或重新附加到实例,系统会将 attachVolume
或 reattachVolume
事件发送至您的 AWS 账户。不过,不会保存、记录或存档该事件。如果您使用KMS密钥加密EBS卷并且该KMS密钥失效,则该密KMS钥稍后用于连接或重新连接到实例时EBS将发出一个事件,如以下示例所示。
事件数据
下面的列表是失败attachVolume
事件发生EBS后发射的JSON对象的示例。失败的原因是KMS密钥有待删除。
注意
AWS 服务器例行维护后,可能会尝试重新连接到卷。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-0123456789ab
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
:0123456789ab
:volume/vol-01234567
",
"arn:aws:kms:us-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
"
],
"detail": {
"event": "attachVolume",
"result": "failed",
"cause": "arn:aws:kms:us-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
is pending deletion.",
"request-id": ""
}
}
下面的列表是失败reattachVolume
事件发生EBS后发射的JSON对象的示例。失败的原因是KMS密钥有待删除。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-0123456789ab
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
:0123456789ab
:volume/vol-01234567
",
"arn:aws:kms:us-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
"
],
"detail": {
"event": "reattachVolume",
"result": "failed",
"cause": "arn:aws:kms:us-east-1
:0123456789ab
:key/01234567
-0123
-0123
-0123
-0123456789ab
is pending deletion.",
"request-id": ""
}
}
分离音量 () detachVolume
当卷与 Amazon EC2 实例分离时,该detachVolume
事件将发送到您的 AWS 账户。
事件数据
以下是成功detachVolume
事件的示例。
{
"version":"0",
"id":"2ec37298-1234-e436-70fc-c96b1example
",
"detail-type":"AWS API Call via CloudTrail",
"source":"aws.ec2",
"account":"123456789012
",
"time":"2024-03-18T16:35:52Z
",
"region":"us-east-1
",
"resources":[],
"detail":
{
"eventVersion":"1.09",
"userIdentity":
{
"type":"IAMUser",
"principalId":"AIDAJT12345SQ2EXAMPLE
",
"arn":"arn:aws:iam::123456789012:user/administrator"
,
"accountId":"123456789012"
,
"accessKeyId":"AKIAJ67890A6EXAMPLE"
,
"userName":"administrator
"
},
"eventTime":"2024-03-18T16:35:52Z
",
"eventSource":"ec2.amazonaws.com",
"eventName":"DetachVolume",
"awsRegion":"us-east-1
",
"sourceIPAddress":"12.12.123.12
",
"userAgent":"aws-cli/2.7.12 Python/3.9.11 Windows/10 exe/AMD64 prompt/off command/ec2.detach-volume",
"requestParameters":
{
"volumeId":"vol-072577c46bexample
",
"force":false
},
"responseElements":
{
"requestId":"1234513a-6292-49ea-83f8-85e95example
",
"volumeId":"vol-072577c46bexample
",
"instanceId":"i-0217f7eb3dexample
",
"device":"/dev/sdb
",
"status":"detaching",
"attachTime":1710776815000
},
"requestID":"1234513a-6292-49ea-83f8-85e95example
",
"eventID":"1234551d-a15a-43eb-9e69-c983aexample
",
"readOnly":false,
"eventType":"AwsApiCall",
"managementEvent":true,
"recipientAccountId":"123456789012
",
"eventCategory":"Management",
"tlsDetails":
{
"tlsVersion":"TLSv1.3",
"cipherSuite":"TLS_AES_128_GCM_SHA256",
"clientProvidedHostHeader":"ec2.us-east-1.amazonaws.com
"
}
}
}
EBS音量修改事件
修改卷 EventBridge 时,Amazon EBS 会向发送modifyVolume
事件。不过,不会保存、记录或存档该事件。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
:012345678901
:volume/vol-03a55cf56513fa1b6
"
],
"detail": {
"result": "optimizing
",
"cause": "",
"event": "modifyVolume",
"request-id": "01234567
-0123
-0123
-0123
-0123456789ab
"
}
}
EBS快照事件
当发生以下卷事件 EventBridge 时,Amazon 会EBS向发送事件。
创建快照 (createSnapshot)
创建快照的操作完成后,该createSnapshot
事件就会发送到您的 AWS 账户。不过,不会保存、记录或存档该事件。此事件的结果可能是 succeeded
或 failed
。
事件数据
下面的列表是成功createSnapshot
事件所发射的JSON对象EBS的示例。在该detail
部分中,该source
字段包含源卷的。ARNstartTime
和 endTime
字段表示快照的创建何时开始以及何时完成。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Snapshot Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-west-2
:snapshot/snap-01234567
"
],
"detail": {
"event": "createSnapshot",
"result": "succeeded",
"cause": "",
"request-id": "",
"snapshot_id": "arn:aws:ec2::us-west-2
:snapshot/snap-01234567
",
"source": "arn:aws:ec2::us-west-2
:volume/vol-01234567
",
"startTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"endTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z" }
}
创建快照 (createSnapshots)
创建多卷快照的操作完成后,该createSnapshots
事件就会发送到您的 AWS 账户。此事件的结果可能是 succeeded
或 failed
。
事件数据
下面的列表是成功createSnapshots
事件所发射的JSON对象EBS的示例。在该detail
部分中,该source
字段包含多卷快照集的源卷。ARNsstartTime
和 endTime
字段表示快照的创建何时开始以及何时完成。
{
"version": "0",
"id": "01234567-0123-0123-0123-012345678901
",
"detail-type": "EBS Multi-Volume Snapshots Completion Status",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-east-1
:snapshot/snap-01234567
",
"arn:aws:ec2::us-east-1
:snapshot/snap-012345678
"
],
"detail": {
"event": "createSnapshots",
"result": "succeeded",
"cause": "",
"request-id": "",
"startTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"endTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"snapshots": [
{
"snapshot_id": "arn:aws:ec2::us-east-1
:snapshot/snap-01234567
",
"source": "arn:aws:ec2::us-east-1
:volume/vol-01234567
",
"status": "completed"
},
{
"snapshot_id": "arn:aws:ec2::us-east-1
:snapshot/snap-012345678
",
"source": "arn:aws:ec2::us-east-1
:volume/vol-012345678
",
"status": "completed"
}
]
}
}
下面的列表是失败createSnapshots
事件发生EBS后发射的JSON对象的示例。失败的原因是多卷快照集的一个或多个快照未能完成。的值snapshot_id
是失败快照ARNs的值。 startTime
并endTime
表示创建快照操作的开始和结束时间。
{
"version": "0",
"id": "01234567-0123-0123-0123-012345678901
",
"detail-type": "EBS Multi-Volume Snapshots Completion Status",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy-mm-ddThh:mm:ssZ
",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-east-1
:snapshot/snap-01234567
",
"arn:aws:ec2::us-east-1
:snapshot/snap-012345678
"
],
"detail": {
"event": "createSnapshots",
"result": "failed",
"cause": "Snapshot snap-01234567 is in status error",
"request-id": "",
"startTime": "yyyy-mm-ddThh:mm:ssZ
",
"endTime": "yyyy-mm-ddThh:mm:ssZ
",
"snapshots": [
{
"snapshot_id": "arn:aws:ec2::us-east-1
:snapshot/snap-01234567
",
"source": "arn:aws:ec2::us-east-1
:volume/vol-01234567
",
"status": "error"
},
{
"snapshot_id": "arn:aws:ec2::us-east-1
:snapshot/snap-012345678
",
"source": "arn:aws:ec2::us-east-1
:volume/vol-012345678
",
"status": "error"
}
]
}
}
复制快照 (copySnapshot)
复制快照的操作完成后,该copySnapshot
事件就会发送到您的 AWS 账户。不过,不会保存、记录或存档该事件。此事件的结果可能是 succeeded
或 failed
。
如果您要跨区域复制快照,则事件将在目标区域中发出。
事件数据
下面的列表是成功copySnapshot
事件EBS后发射的JSON对象的示例。的值snapshot_id
是新创建ARN的快照的。在该detail
部分中,的值source
是ARN源快照的。 startTime
并endTime
表示复制快照操作的开始和结束时间。 incremental
表示快照是增量快照 (true
) 还是完整快照 (false
)。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Snapshot Notification",
"source": "aws.ec2",
"account": "123456789012
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-west-2
:snapshot/snap-01234567
"
],
"detail": {
"event": "copySnapshot",
"result": "succeeded",
"cause": "",
"request-id": "",
"snapshot_id": "arn:aws:ec2::us-west-2
:snapshot/snap-01234567
",
"source": "arn:aws:ec2::eu-west-1
:snapshot/snap-76543210
",
"startTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"endTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"incremental": "true"
}
}
下面的列表是失败copySnapshot
事件发生EBS后发射的JSON对象的示例。失败原因是源快照 ID 无效。的值snapshot_id
是失败ARN的快照的值。在该detail
部分中,的值source
是ARN源快照的。 startTime
并endTime
表示复制快照操作的开始和结束时间。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Snapshot Notification",
"source": "aws.ec2",
"account": "123456789012
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-west-2
:snapshot/snap-01234567
"
],
"detail": {
"event": "copySnapshot",
"result": "failed",
"cause": "Source snapshot ID is not valid",
"request-id": "",
"snapshot_id": "arn:aws:ec2::us-west-2
:snapshot/snap-01234567
",
"source": "arn:aws:ec2::eu-west-1
:snapshot/snap-76543210
",
"startTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"endTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z"
}
}
共享快照 (shareSnapshot)
当另一个 AWS 账户与其共享快照时,该shareSnapshot
事件就会发送到您的账户。不过,不会保存、记录或存档该事件。结果始终是 succeeded
。
事件数据
以下是shareSnapshot
事件完成EBS后发射的JSON对象的示例。在该detail
部分中,的值source
是与您共享快照的用户的 AWS 账号。 startTime
并endTime
表示共享快照操作的开始和结束时间。仅在与其他用户共享私有快照时,系统才会发送 shareSnapshot
事件。共享公有快照不会触发该事件。
{
"version": "0",
"id": "01234567
-01234
-0123
-0123
-012345678901
",
"detail-type": "EBS Snapshot Notification",
"source": "aws.ec2",
"account": "012345678901
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2::us-west-2
:snapshot/snap-01234567
"
],
"detail": {
"event": "shareSnapshot",
"result": "succeeded",
"cause": "",
"request-id": "",
"snapshot_id": "arn:aws:ec2::us-west-2
:snapshot/snap-01234567
",
"source": 012345678901
,
"startTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"endTime": "yyyy
-mm
-dd
Thh
:mm
:ss
Z"
}
}
EBS快照存档事件
Amazon 会EBS发出与快照存档操作相关的事件。有关更多信息,请参阅监控快照归档。
EBS快速快照恢复事件
当快照的快速还原状态发生变化 EventBridge 时,Amazon 会EBS向发送事件。尽最大努力发出事件。
以下是此事件的示例数据。
{
"version": "0",
"id": "01234567
-0123
-0123
-0123
-012345678901
",
"detail-type": "EBS Fast Snapshot Restore State-change Notification",
"source": "aws.ec2",
"account": "123456789012
",
"time": "yyyy
-mm
-dd
Thh
:mm
:ss
Z",
"region": "us-east-1
",
"resources": [
"arn:aws:ec2:us-east-1
::snapshot/snap-03a55cf56513fa1b6
"
],
"detail": {
"snapshot-id": "snap-1234567890abcdef0
",
"state": "optimizing
",
"zone": "us-east-1a
",
"message": "Client.UserInitiated - Lifecycle state transition
",
}
}
可能的 state
值为 enabling
、optimizing
、enabled
、disabling
和 disabled
。
message
的可能值如下所示:
Client.InvalidSnapshot.InvalidState - The requested snapshot transitioned to an invalid state (Error)
-
启用快速快照还原的请求失败,并且状态转换为
disabling
或disabled
。无法为该快照启用快速快照还原。 Client.UserInitiated
-
状态成功转换为
enabling
或disabling
。 Client.UserInitiated - Lifecycle state transition
-
状态成功转换为
optimizing
、enabled
或disabled
。 Server.InsufficientCapacity - There was insufficient capacity available to satisfy the request
-
由于容量不足而导致启用快速快照还原的请求失败,并且状态转换为
disabling
或disabled
。等待,然后重试。 Server.InternalError - An internal error caused the operation to fail
-
由于内部错误而导致启用快速快照还原的请求失败,并且状态转换为
disabling
或disabled
。等待,然后重试。 Client.InvalidSnapshot.InvalidState - The requested snapshot was deleted or access permissions were revoked
-
快照的快速快照还原状态已转换为
disabling
或disabled
,因为快照已被快照所有者删除或取消共享。无法为已删除或不再与您共享的快照启用快速快照还原。
AWS Lambda 用于处理 EventBridge 事件
您可以使用 Amazon EBS 和 Amazon EventBridge 来自动执行数据备份工作流程。这要求您创建IAM策略、处理事件的 AWS Lambda 函数以及匹配传入事件并将其路由到 Lambda 函数的 EventBridge规则。
以下过程使用 createSnapshot
事件自动将已完成的快照复制到其他区域,以用于灾难恢复。
将已完成的快照复制到其他区域
-
创建IAM策略(如以下示例所示的策略),以提供使用该
CopySnapshot
操作和写入 EventBridge 日志的权限。将策略分配给将处理 EventBridge 事件的用户。{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:PutLogEvents" ], "Resource": "arn:aws:logs:*:*:*" }, { "Effect": "Allow", "Action": [ "ec2:CopySnapshot" ], "Resource": "*" } ] }
-
在 Lambda 中定义一个可在控制台中使用的函数。 EventBridge 下面用 Node.js 编写的示例 Lambda 函数是在亚马逊发出匹配
createSnapshot
的事件EBS(表示快照已完成) EventBridge 时调用的。该函数被调用后,它会将快照从us-east-2
复制到us-east-1
。// Sample Lambda function to copy an EBS snapshot to a different Region var AWS = require('aws-sdk'); var ec2 = new AWS.EC2(); // define variables var destinationRegion = '
us-east-1
'; var sourceRegion = 'us-east-2
'; console.log ('Loading function'); //main function exports.handler = (event, context, callback) => { // Get the EBS snapshot ID from the event details var snapshotArn = event.detail.snapshot_id.split('/'); const snapshotId = snapshotArn[1]; const description = `Snapshot copy from ${snapshotId} in ${sourceRegion}.`; console.log ("snapshotId:", snapshotId); // Load EC2 class and update the configuration to use destination Region to initiate the snapshot. AWS.config.update({region: destinationRegion}); var ec2 = new AWS.EC2(); // Prepare variables for ec2.modifySnapshotAttribute call const copySnapshotParams = { Description: description, DestinationRegion: destinationRegion, SourceRegion: sourceRegion, SourceSnapshotId: snapshotId }; // Execute the copy snapshot and log any errors ec2.copySnapshot(copySnapshotParams, (err, data) => { if (err) { const errorMessage = `Error copying snapshot ${snapshotId} to Region ${destinationRegion}.`; console.log(errorMessage); console.log(err); callback(errorMessage); } else { const successMessage = `Successfully started copy of snapshot ${snapshotId} to Region ${destinationRegion}.`; console.log(successMessage); console.log(data); callback(null, successMessage); } }); };为确保您的 Lambda 函数可在 EventBridge 控制台中使用,请在 EventBridge 事件发生的区域创建该函数。有关更多信息,请参见AWS Lambda 开发人员指南。
打开 Amazon EventBridge 控制台,网址为https://console.aws.amazon.com/events/
。 -
在导航窗格中,选择规则,然后选择创建规则。
-
对于 Step 1: Define rule detail(步骤 1:定义规则详细信息),请执行以下操作:
-
为 Name(名称)和 Description(描述)输入值。
-
对于 Event bus(事件总线),保持 default(默认)。
-
确保 Enable the rule on the selected event bus(在选定的事件总线上启用该规则)已开启。
-
对于 Event type(事件类型),选择 Rule with an event pattern(具有事件模式的规则)。
-
选择下一步。
-
-
对于 Step 2: Build event pattern(步骤 2:构建事件模式),执行以下操作:
-
在事件源中,选择AWS 事件或 EventBridge 合作伙伴事件。
-
在事件模式部分中,对于事件源,确保选择了AWS 服务,对于AWS 服务,请选择EC2。
-
对于 “事件类型”,选择 “EBS快照通知”,选择 “特定事件”,然后选择createSnapshot。
-
选择特定结果,然后选择已成功。
-
选择下一步。
-
-
对于 Step 3: Select targets(步骤 3:选择目标),请执行以下操作:
-
对于目标类型,选择AWS 服务。
-
对于 Select target(选择目标),选择 Lambda function(Lambda 函数),对于 Function(函数),选择之前创建的函数。
-
选择 Next(下一步)。
-
-
对于 Step 4: Configure tags(步骤 4:配置标签),如果需要,为规则指定标签,然后选择 Next(下一步)。
-
对于 Step 5: Review and create(步骤 5:查看并创建),查看规则,然后选择 Create rule(创建规则)。
现在,您的规则应该会显示在规则选项卡中。在所示的示例中,您配置的事件应EBS在下次复制快照时触发。