Beispiele für CloudWatch Events aus unterstützten Services - Amazon CloudWatch Events

Beispiele für CloudWatch Events aus unterstützten Services

Anmerkung

Amazon EventBridge ist die bevorzugte Methode zum Verwalten Ihrer Ereignisse. Amazon CloudWatch Events und EventBridge liegen der gleiche Service und die gleiche API zugrunde, EventBridge bietet jedoch mehr Funktionen. Änderungen, die Sie in CloudWatch oder EventBridge vornehmen, werden in allen Konsolen angezeigt. Weitere Informationen finden Sie unter Amazon EventBridge.

Die hier aufgeführten AWS-Services geben Ereignisse aus, die von CloudWatch Events erkannt werden können.

Darüber hinaus können Sie CloudWatch Events auch für Dienste verwenden, die keine Ereignisse ausgeben und nicht auf dieser Seite aufgeführt sind, indem Sie auf Ereignisse achten, die über CloudTrail geliefert werden. Weitere Informationen finden Sie unter Über CloudTrail übermittelte Ereignisse.

Ereignisse von Amazon Augmented AI

Beispiele für Ereignisse, die von Amazon Augmented AI generiert werden, finden Sie unter Verwenden von Ereignissen in Amazon Augmented AI.

Application Auto Scaling Ereignisse

Beispiele für Ereignisse, die von generiert werden, finden Sie unter Application Auto Scaling-Ereignisse und EventBridge.

AWS Batch-Ereignisse

Beispiele für von AWS Batch erstellte Ereignisse finden Sie unter AWS Batch-Ereignisse.

Geplante Ereignisse von Amazon CloudWatch Events

Es folgt ein Beispiel für ein geplantes Ereignis:

{ "id": "53dc4d37-cffa-4f76-80c9-8b7d4a4d2eaa", "detail-type": "Scheduled Event", "source": "aws.events", "account": "123456789012", "time": "2019-10-08T16:53:06Z", "region": "us-east-1", "resources": [ "arn:aws:events:us-east-1:123456789012:rule/MyScheduledRule" ], "detail": {} }

Amazon Chime Events

Beispiele für Ereignisse, die von generiert werden, finden Sie unter Automatisieren von Amazon Chime mit EventBridge.

Ereignisse von CloudWatch

Beispielereignisse von CloudWatch finden Sie unter Alarmereignisse und EventBridge im AWS CodeBuild Benutzerhandbuch .

CodeBuild Ereignisse

CodeBuild Beispielereignisse finden Sie unter Build Notifications Eingabeformat-Referenz imAWS CodeBuildBenutzerhandbuch.

CodeCommit Ereignisse

Informationen zu CodeCommit-Beispielereignissen finden Sie unterÜberwachung von CodeCommit-Ereignissen in EventBridge und CloudWatch EventsimAWS CodeCommitBenutzerhandbuch.

AWS CodeDeploy-Ereignisse

Es folgen Beispiele der Ereignisse für CodeDeploy. Weitere Informationen finden Sie unterÜberwachen von Bereitstellungen mit CloudWatch Events im AWS CodeDeploy Benutzerhandbuch.

Benachrichtigung über die Änderung des Bereitstellungsstatus in CodeDeploy

Es wurde eine Änderung am Status einer Bereitstellung vorgenommen.

{ "account": "123456789012", "region": "us-east-1", "detail-type": "CodeDeploy Deployment State-change Notification", "source": "aws.codedeploy", "version": "0", "time": "2016-06-30T22:06:31Z", "id": "c071bfbf-83c4-49ca-a6ff-3df053957145", "resources": [ "arn:aws:codedeploy:us-east-1:123456789012:application:myApplication", "arn:aws:codedeploy:us-east-1:123456789012:deploymentgroup:myApplication/myDeploymentGroup" ], "detail": { "instanceGroupId": "9fd2fbef-2157-40d8-91e7-6845af69e2d2", "region": "us-east-1", "application": "myApplication", "deploymentId": "d-123456789", "state": "SUCCESS", "deploymentGroup": "myDeploymentGroup" } }

Benachrichtigung über die Statusänderung für eine CodeDeploy-Instance

Es wurde eine Änderung am Status einer Instance vorgenommen, die zu einer Bereitstellungsgruppe gehört.

{ "account": "123456789012", "region": "us-east-1", "detail-type": "CodeDeploy Instance State-change Notification", "source": "aws.codedeploy", "version": "0", "time": "2016-06-30T23:18:50Z", "id": "fb1d3015-c091-4bf9-95e2-d98521ab2ecb", "resources": [ "arn:aws:ec2:us-east-1:123456789012:instance/i-0000000aaaaaaaaaa", "arn:aws:codedeploy:us-east-1:123456789012:deploymentgroup:myApplication/myDeploymentGroup", "arn:aws:codedeploy:us-east-1:123456789012:application:myApplication" ], "detail": { "instanceId": "i-0000000aaaaaaaaaa", "region": "us-east-1", "state": "SUCCESS", "application": "myApplication", "deploymentId": "d-123456789", "instanceGroupId": "8cd3bfa8-9e72-4cbe-a1e5-da4efc7efd49", "deploymentGroup": "myDeploymentGroup" } }

CodePipeline-Ereignisse

Es folgen Beispiele der Ereignisse für CodePipeline.

Statusänderung bei der Pipeline-Ausführung

{ "version": "0", "id": "CWE-event-id", "detail-type": "CodePipeline Pipeline Execution State Change", "source": "aws.codepipeline", "account": "123456789012", "time": "2017-04-22T03:31:47Z", "region": "us-east-1", "resources": [ "arn:aws:codepipeline:us-east-1:123456789012:pipeline:myPipeline" ], "detail": { "pipeline": "myPipeline", "version": "1", "state": "STARTED", "execution-id": "01234567-0123-0123-0123-012345678901" } }

Statusänderung bei der Stufenausführung

{ "version": "0", "id": "CWE-event-id", "detail-type": "CodePipeline Stage Execution State Change", "source": "aws.codepipeline", "account": "123456789012", "time": "2017-04-22T03:31:47Z", "region": "us-east-1", "resources": [ "arn:aws:codepipeline:us-east-1:123456789012:pipeline:myPipeline" ], "detail": { "pipeline": "myPipeline", "version": "1", "execution-id": "01234567-0123-0123-0123-012345678901", "stage": "Prod", "state": "STARTED" } }

Statusänderung bei der Aktionsausführung

Dieses Beispiel enthält zwei region-Felder. Das oben ist der Name der AWS-Region, in der die Aktion in der Ziel-Pipeline ausgeführt wird. In diesem Beispiel lautet diese us-east-1. Die region im detail-Abschnitt ist die AWS-Region, in der das Ereignis erstellt wurde. Dies ist die gleiche wie die Region, in der die Pipeline erstellt wurde. In diesem Beispiel lautet diese us-west-2.

{ "version": "0", "id": "CWE-event-id", "detail-type": "CodePipeline Action Execution State Change", "source": "aws.codepipeline", "account": "123456789012", "time": "2017-04-22T03:31:47Z", "region": "us-east-1", "resources": [ "arn:aws:codepipeline:us-east-1:123456789012:pipeline:myPipeline" ], "detail": { "pipeline": "myPipeline", "version": 1, "execution-id": "01234567-0123-0123-0123-012345678901", "stage": "Prod", "action": "myAction", "state": "STARTED", "region":"us-west-2", "type": { "owner": "AWS", "category": "Deploy", "provider": "CodeDeploy", "version": 1 } } }

AWS Config-Ereignisse

Weitere Informationen zu denAWS Config-Ereignisse finden Sie unterÜberwachungAWS Configmit Amazon CloudWatch EventsimAWS ConfigEntwicklerhandbuchaus.

Amazon EBS-Ereignisse

Weitere Informationen zu den Amazon EBS-Ereignissen finden Sie unterAmazon CloudWatch Events für Amazon EBSimAmazon EC2-Benutzerhandbuch für Linux-Instances.

Amazon EC2 Auto Scaling-Gruppen Ereignisse

Weitere Informationen zu den Auto Scaling Events finden Sie unterAbrufen von CloudWatch Events, wenn Ihre Auto Sclaing Gruppe skaliert wirdimBenutzerhandbuch für Amazon EC2 Auto Scaling.

Amazon EC2 Instance Rebalance Recommendation Events Ereignisse

Weitere Informationen zu den Ereignissen für EC2-Instance-Neuausgleichsempfehlungen finden Sie unter Überwachen von Signalen für Neuausgleich im Amazon EC2-Benutzerhandbuch für Linux-Instances.

Amazon EC2-Spot-Instance-Unterbrechungsereignisse

Ein Beispiel für eine Unterbrechung von Spot-Instances finden Sie unter Benachrichtigungen über Spot-Instance-Unterbrechungen im Amazon EC2-Benutzerhandbuch für Linux-Instances.

Änderungsereignisse des -Amazon EC2 Status

Im Folgenden finden Sie ein Beispiel für die Ereignisse für Amazon EC2-Instances, wenn sich der Instance-Status ändert.

Benachrichtigung über die Statusänderung für eine EC2-Instance

Dies ist das Beispiel einer Instance im Status pending. Die anderen mögliche Werte für state sind runningshutting-down, stopped, stopping und terminated.

{ "id":"7bf73129-1428-4cd3-a780-95db273d1602", "detail-type":"EC2 Instance State-change Notification", "source":"aws.ec2", "account":"123456789012", "time":"2019-11-11T21:29:54Z", "region":"us-east-1", "resources":[ "arn:aws:ec2:us-east-1:123456789012:instance/i-abcd1111" ], "detail":{ "instance-id":"i-abcd1111", "state":"pending" } }

Amazon Elastic Container-Registry Ereignisse

Amazon ECR sendet Abbild-Aktionsereignisse an EventBridge. Ereignisse werden gesendet, wenn Abbilder verschoben, gescannt oder gelöscht werden.

Informationen zu Amazon ECS-Beispielereignissen finden Sie unterEreignisse für Amazon ECRimBenutzerhandbuch für Amazon Elastic Container Registryaus.

Amazon Elastic Container Service Ereignisse

Amazon ECS sendet zwei Arten von Ereignissen an EventBridge: Container-Instance-Ereignisse und Aufgabenereignisse. Container-Instance-Ereignisse werden nur gesendet, wenn Sie für Ihre Aufgaben den Starttyp EC2 verwenden. Für Aufgaben, die den Starttyp Fargate verwenden, erhalten Sie ausschließlich Aufgabenstatusereignisse. Amazon ECS verfolgt den Status Ihrer Container-Instances und Aufgaben. Wenn sich eine der beiden Ressourcen ändert, wird ein Ereignis ausgelöst. Diese Ereignisse werden entweder als Änderungsereignisse des Container-Instance-Status oder als Änderungsereignisse des Aufgabenstatus klassifiziert.

Informationen zu Amazon ECS-Beispielereignissen finden Sie unterEreignisse für Amazon ECS-EreignisseimEntwicklerhandbuch für Amazon Elastic Container Serviceaus.

AWS Elemental MediaConvert Ereignisse

Weitere Informationen zu Beispielereignissen von MediaConvert finden Sie unterVerwenden von CloudWatch Events zum Überwachen von AWS Elemental MediaConvert AufträgenimBenutzerhandbuch für AWS Elemental MediaConvert.

AWS Elemental MediaPackage Ereignisse

Informationen zu Beispielereignissen für MediaPackage finden Sie unterÜberwachen von AWS Elemental MediaPackage mit Amazon CloudWatch EventsimAWS Elemental MediaPackage — Benutzerhandbuchaus.

AWS Elemental MediaStore Ereignisse

Informationen zu MediaStore Beispielereignissen finden Sie unterAutomatisieren von AWS Elemental MediaStore mit CloudWatch EventsimAWS Elemental MediaStore — Benutzerhandbuchaus.

Ereignisse für Amazon EMR

Von Amazon EMR gemeldete Ereignisse haben aws.emr als Wert für Source, während über CloudTrail gemeldete Amazon EMR-API-Ereignisse aws.elasticmapreduce als Wert für Source haben.

Es folgen Beispiele von Ereignissen, die von Amazon EMR gemeldet werden.

Statusänderung der Auto-Scaling-Richtlinie in Amazon EMR

{ "version":"0", "id":"2f8147ab-8c48-47c6-b0b6-3ee23ec8d300", "detail-type":"EMR Auto Scaling Policy State Change", "source":"aws.emr", "account":"123456789012", "time":"2016-12-16T20:42:44Z", "region":"us-east-1", "resources":[], "detail":{ "resourceId":"ig-X2LBMHTGPCBU", "clusterId":"j-1YONHTCP3YZKC", "state":"PENDING", "message":"AutoScaling policy modified by user request", "scalingResourceType":"INSTANCE_GROUP" } }

Amazon-EMR-Cluster-Statusänderung – Start

{ "version": "0", "id": "999cccaa-eaaa-0000-1111-123456789012", "detail-type": "EMR Cluster State Change", "source": "aws.emr", "account": "123456789012", "time": "2016-12-16T20:43:05Z", "region": "us-east-1", "resources": [], "detail": { "severity": "INFO", "stateChangeReason": "{\"code\":\"\"}", "name": "Development Cluster", "clusterId": "j-123456789ABCD", "state": "STARTING", "message": "Amazon EMR cluster j-123456789ABCD (Development Cluster) was requested at 2016-12-16 20:42 UTC and is being created." } }

Amazon-EMR-Cluster-Statusänderung – Beendet

{ "version": "0", "id": "1234abb0-f87e-1234-b7b6-000000123456", "detail-type": "EMR Cluster State Change", "source": "aws.emr", "account": "123456789012", "time": "2016-12-16T21:00:23Z", "region": "us-east-1", "resources": [], "detail": { "severity": "INFO", "stateChangeReason": "{\"code\":\"USER_REQUEST\",\"message\":\"Terminated by user request\"}", "name": "Development Cluster", "clusterId": "j-123456789ABCD", "state": "TERMINATED", "message": "Amazon EMR Cluster jj-123456789ABCD (Development Cluster) has terminated at 2016-12-16 21:00 UTC with a reason of USER_REQUEST." } }

Statusänderung von Amazon-EMR-Instance-Gruppen

{ "version": "0", "id": "999cccaa-eaaa-0000-1111-123456789012", "detail-type": "EMR Instance Group State Change", "source": "aws.emr", "account": "123456789012", "time": "2016-12-16T20:57:47Z", "region": "us-east-1", "resources": [], "detail": { "market": "ON_DEMAND", "severity": "INFO", "requestedInstanceCount": "2", "instanceType": "m3.xlarge", "instanceGroupType": "CORE", "instanceGroupId": "ig-ABCDEFGHIJKL", "clusterId": "j-123456789ABCD", "runningInstanceCount": "2", "state": "RUNNING", "message": "The resizing operation for instance group ig-ABCDEFGHIJKL in Amazon EMR cluster j-123456789ABCD (Development Cluster) is complete. It now has an instance count of 2. The resize started at 2016-12-16 20:57 UTC and took 0 minutes to complete." } }

Amazon-EMR-Schritt-Statusänderung

{ "version": "0", "id": "999cccaa-eaaa-0000-1111-123456789012", "detail-type": "EMR Step Status Change", "source": "aws.emr", "account": "123456789012", "time": "2016-12-16T20:53:09Z", "region": "us-east-1", "resources": [], "detail": { "severity": "ERROR", "actionOnFailure": "CONTINUE", "stepId": "s-ZYXWVUTSRQPON", "name": "CustomJAR", "clusterId": "j-123456789ABCD", "state": "FAILED", "message": "Step s-ZYXWVUTSRQPON (CustomJAR) in Amazon EMR cluster j-123456789ABCD (Development Cluster) failed at 2016-12-16 20:53 UTC." } }

Amazon GameLift Event

Es folgen Beispiele von Amazon GameLift-Ereignissen. Weitere Informationen finden Sie unter FlexMatch Events Reference im Amazon GameLift-Entwicklerhandbuch.

Matchmaking Searching

{ "version": "0", "id": "cc3d3ebe-1d90-48f8-b268-c96655b8f013", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-08T21:15:36.421Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-08T21:15:35.676Z", "players": [ { "playerId": "player-1" } ] } ], "estimatedWaitMillis": "NOT_AVAILABLE", "type": "MatchmakingSearching", "gameSessionInfo": { "players": [ { "playerId": "player-1" } ] } } }

Potenzielles Match erstellt

{ "version": "0", "id": "fce8633f-aea3-45bc-aeba-99d639cad2d4", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-08T21:17:41.178Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-08T21:15:35.676Z", "players": [ { "playerId": "player-1", "team": "red" } ] }, { "ticketId": "ticket-2", "startTime": "2017-08-08T21:17:40.657Z", "players": [ { "playerId": "player-2", "team": "blue" } ] } ], "acceptanceTimeout": 600, "ruleEvaluationMetrics": [ { "ruleName": "EvenSkill", "passedCount": 3, "failedCount": 0 }, { "ruleName": "EvenTeams", "passedCount": 3, "failedCount": 0 }, { "ruleName": "FastConnection", "passedCount": 3, "failedCount": 0 }, { "ruleName": "NoobSegregation", "passedCount": 3, "failedCount": 0 } ], "acceptanceRequired": true, "type": "PotentialMatchCreated", "gameSessionInfo": { "players": [ { "playerId": "player-1", "team": "red" }, { "playerId": "player-2", "team": "blue" } ] }, "matchId": "3faf26ac-f06e-43e5-8d86-08feff26f692" } }

AcceptMatch

{ "version": "0", "id": "b3f76d66-c8e5-416a-aa4c-aa1278153edc", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-09T20:04:42.660Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-09T20:01:35.305Z", "players": [ { "playerId": "player-1", "team": "red" } ] }, { "ticketId": "ticket-2", "startTime": "2017-08-09T20:04:16.637Z", "players": [ { "playerId": "player-2", "team": "blue", "accepted": false } ] } ], "type": "AcceptMatch", "gameSessionInfo": { "players": [ { "playerId": "player-1", "team": "red" }, { "playerId": "player-2", "team": "blue", "accepted": false } ] }, "matchId": "848b5f1f-0460-488e-8631-2960934d13e5" } }

Accept Match abgeschlossen

{ "version": "0", "id": "b1990d3d-f737-4d6c-b150-af5ace8c35d3", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-08T20:43:14.621Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-08T20:30:40.972Z", "players": [ { "playerId": "player-1", "team": "red" } ] }, { "ticketId": "ticket-2", "startTime": "2017-08-08T20:33:14.111Z", "players": [ { "playerId": "player-2", "team": "blue" } ] } ], "acceptance": "TimedOut", "type": "AcceptMatchCompleted", "gameSessionInfo": { "players": [ { "playerId": "player-1", "team": "red" }, { "playerId": "player-2", "team": "blue" } ] }, "matchId": "a0d9bd24-4695-4f12-876f-ea6386dd6dce" } }

Matchmaking erfolgreich

{ "version": "0", "id": "5ccb6523-0566-412d-b63c-1569e00d023d", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-09T19:59:09.159Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-09T19:58:59.277Z", "players": [ { "playerId": "player-1", "playerSessionId": "psess-6e7c13cf-10d6-4756-a53f-db7de782ed67", "team": "red" } ] }, { "ticketId": "ticket-2", "startTime": "2017-08-09T19:59:08.663Z", "players": [ { "playerId": "player-2", "playerSessionId": "psess-786b342f-9c94-44eb-bb9e-c1de46c472ce", "team": "blue" } ] } ], "type": "MatchmakingSucceeded", "gameSessionInfo": { "gameSessionArn": "arn:aws:gamelift:us-west-2:123456789012:gamesession/836cf48d-bcb0-4a2c-bec1-9c456541352a", "ipAddress": "192.168.1.1", "port": 10777, "players": [ { "playerId": "player-1", "playerSessionId": "psess-6e7c13cf-10d6-4756-a53f-db7de782ed67", "team": "red" }, { "playerId": "player-2", "playerSessionId": "psess-786b342f-9c94-44eb-bb9e-c1de46c472ce", "team": "blue" } ] }, "matchId": "c0ec1a54-7fec-4b55-8583-76d67adb7754" } }

Matchmaking abgelaufen

{ "version": "0", "id": "fe528a7d-46ad-4bdc-96cb-b094b5f6bf56", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-09T20:11:35.598Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "reason": "TimedOut", "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-09T20:01:35.305Z", "players": [ { "playerId": "player-1", "team": "red" } ] } ], "ruleEvaluationMetrics": [ { "ruleName": "EvenSkill", "passedCount": 3, "failedCount": 0 }, { "ruleName": "EvenTeams", "passedCount": 3, "failedCount": 0 }, { "ruleName": "FastConnection", "passedCount": 3, "failedCount": 0 }, { "ruleName": "NoobSegregation", "passedCount": 3, "failedCount": 0 } ], "type": "MatchmakingTimedOut", "message": "Removed from matchmaking due to timing out.", "gameSessionInfo": { "players": [ { "playerId": "player-1", "team": "red" } ] } } }

Matchmaking abgebrochen

{ "version": "0", "id": "8d6f84da-5e15-4741-8d5c-5ac99091c27f", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-09T20:00:07.843Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "reason": "Cancelled", "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-09T19:59:26.118Z", "players": [ { "playerId": "player-1" } ] } ], "ruleEvaluationMetrics": [ { "ruleName": "EvenSkill", "passedCount": 0, "failedCount": 0 }, { "ruleName": "EvenTeams", "passedCount": 0, "failedCount": 0 }, { "ruleName": "FastConnection", "passedCount": 0, "failedCount": 0 }, { "ruleName": "NoobSegregation", "passedCount": 0, "failedCount": 0 } ], "type": "MatchmakingCancelled", "message": "Cancelled by request.", "gameSessionInfo": { "players": [ { "playerId": "player-1" } ] } } }

Matchmaking fehlgeschlagen

{ "version": "0", "id": "025b55a4-41ac-4cf4-89d1-f2b3c6fd8f9d", "detail-type": "GameLift Matchmaking Event", "source": "aws.gamelift", "account": "123456789012", "time": "2017-08-16T18:41:09.970Z", "region": "us-west-2", "resources": [ "arn:aws:gamelift:us-west-2:123456789012:matchmakingconfiguration/SampleConfiguration" ], "detail": { "tickets": [ { "ticketId": "ticket-1", "startTime": "2017-08-16T18:41:02.631Z", "players": [ { "playerId": "player-1", "team": "red" } ] } ], "customEventData": "foo", "type": "MatchmakingFailed", "reason": "UNEXPECTED_ERROR", "message": "An unexpected error was encountered during match placing.", "gameSessionInfo": { "players": [ { "playerId": "player-1", "team": "red" } ] }, "matchId": "3ea83c13-218b-43a3-936e-135cc570cba7" } }

AWS Glue-Ereignisse

Im Folgenden wird das Format für AWS Glue-Ereignisse angegeben.

Erfolgreiche Job-Ausführung

{ "version":"0", "id":"abcdef00-1234-5678-9abc-def012345678", "detail-type":"Glue Job State Change", "source":"aws.glue", "account":"123456789012", "time":"2017-09-07T18:57:21Z", "region":"us-west-2", "resources":[], "detail":{ "jobName":"MyJob", "severity":"INFO", "state":"SUCCEEDED", "jobRunId":"jr_abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789", "message":"Job run succeeded" } }

Fehlerhafte Job-Ausführung

{ "version":"0", "id":"abcdef01-1234-5678-9abc-def012345678", "detail-type":"Glue Job State Change", "source":"aws.glue", "account":"123456789012", "time":"2017-09-07T06:02:03Z", "region":"us-west-2", "resources":[], "detail":{ "jobName":"MyJob", "severity":"ERROR", "state":"FAILED", "jobRunId":"jr_0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef", "message":"JobName:MyJob and JobRunId:jr_0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef failed to execute with exception Role arn:aws:iam::123456789012:role/Glue_Role should be given assume role permissions for Glue Service." } }

Timeout (Zeitüberschreitung)

{ "version":"0", "id":"abcdef00-1234-5678-9abc-def012345678", "detail-type":"Glue Job State Change", "source":"aws.glue", "account":"123456789012", "time":"2017-11-20T20:22:06Z", "region":"us-east-1", "resources":[], "detail":{ "jobName":"MyJob", "severity":"WARN", "state":"TIMEOUT", "jobRunId":"jr_abc0123456789abcdef0123456789abcdef0123456789abcdef0123456789def", "message":"Job run timed out" } }

Angehaltener Auftrag ausgeführt

{ "version":"0", "id":"abcdef00-1234-5678-9abc-def012345678", "detail-type":"Glue Job State Change", "source":"aws.glue", "account":"123456789012", "time":"2017-11-20T20:22:06Z", "region":"us-east-1", "resources":[], "detail":{ "jobName":"MyJob", "severity":"INFO", "state":"STOPPED", "jobRunId":"jr_abc0123456789abcdef0123456789abcdef0123456789abcdef0123456789def", "message":"Job run stopped" } }

Crawler gestartet

{ "version":"0", "id":"05efe8a2-c309-6884-a41b-3508bcdc9695", "detail-type":"Glue Crawler State Change", "source":"aws.glue", "account":"561226563745", "time":"2017-11-11T01:09:46Z", "region":"us-east-1", "resources":[ ], "detail":{ "accountId":"561226563745", "crawlerName":"S3toS3AcceptanceTestCrawlera470bd94-9e00-4518-8942-e80c8431c322", "startTime":"2017-11-11T01:09:46Z", "state":"Started", "message":"Crawler Started" } }

Crawler erfolgreich

{ "version":"0", "id":"3d675db5-59b9-6388-b8e8-e0a9b6d567a9", "detail-type":"Glue Crawler State Change", "source":"aws.glue", "account":"561226563745", "time":"2017-11-11T01:25:00Z", "region":"us-east-1", "resources":[ ], "detail":{ "tablesCreated":"0", "warningMessage":"N/A", "partitionsUpdated":"0", "tablesUpdated":"0", "message":"Crawler Succeeded", "partitionsDeleted":"0", "accountId":"561226563745", "runningTime (sec)":"7", "tablesDeleted":"0", "crawlerName":"SchedulerTestCrawler51fb3a8b-1015-49f0-a969-ca126680b94b", "completionDate":"2017-11-11T01:25:00Z", "state":"Succeeded", "partitionsCreated":"0", "cloudWatchLogLink":"https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logEventViewer:group=/aws-glue/crawlers;stream=SchedulerTestCrawler51fb3a8b-1015-49f0-a969-ca126680b94b" } }

Crawler fehlgeschlagen

{ "version":"0", "id":"f7965b59-470f-2e06-bb89-a8cebaabefac", "detail-type":"Glue Crawler State Change", "source":"aws.glue", "account":"782104008917", "time":"2017-10-20T05:10:08Z", "region":"us-east-1", "resources":[ ], "detail":{ "crawlerName":"test-crawler-notification", "errorMessage":"Internal Service Exception", "accountId":"1234", "cloudWatchLogLink":"https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logEventViewer:group=/aws-glue/crawlers;stream=test-crawler-notification", "state":"Failed", "message":"Crawler Failed" } }

Job-Ausführung im Start-Status

{ "version":"0", "id":"66fbc5e1-aac3-5e85-63d0-856ec669a050", "detail-type":"Glue Job Run Status", "source":"aws.glue", "account":"123456789012", "time":"2018-04-24T20:57:34Z", "region":"us-east-1", "resources":[], "detail":{ "jobName":"MyJob", "severity":"INFO", "notificationCondition":{ "NotifyDelayAfter":1.0 }, "state":"STARTING", "jobRunId":"jr_6aa58e7a3aa44e2e4c7db2c50e2f7396cb57901729e4b702dcb2cfbbeb3f7a86", "message":"Job is in STARTING state", "startedOn":"2018-04-24T20:55:47.941Z" } }

Job-Ausführung im Ausführungsstatus

{ "version":"0", "id":"66fbc5e1-aac3-5e85-63d0-856ec669a050", "detail-type":"Glue Job Run Status", "source":"aws.glue", "account":"123456789012", "time":"2018-04-24T20:57:34Z", "region":"us-east-1", "resources":[], "detail":{ "jobName":"MyJob", "severity":"INFO", "notificationCondition":{ "NotifyDelayAfter":1.0 }, "state":"RUNNING", "jobRunId":"jr_6aa58e7a3aa44e2e4c7db2c50e2f7396cb57901729e4b702dcb2cfbbeb3f7a86", "message":"Job is in RUNNING state", "startedOn":"2018-04-24T20:55:47.941Z" } }

Job-Ausführung im Stopp-Status

{ "version":"0", "id":"66fbc5e1-aac3-5e85-63d0-856ec669a050", "detail-type":"Glue Job Run Status", "source":"aws.glue", "account":"123456789012", "time":"2018-04-24T20:57:34Z", "region":"us-east-1", "resources":[], "detail":{ "jobName":"MyJob", "severity":"INFO", "notificationCondition":{ "NotifyDelayAfter":1.0 }, "state":"STOPPING", "jobRunId":"jr_6aa58e7a3aa44e2e4c7db2c50e2f7396cb57901729e4b702dcb2cfbbeb3f7a86", "message":"Job is in STOPPING state", "startedOn":"2018-04-24T20:55:47.941Z" } }

Statusänderung von Tabellen des AWS Glue-Datenkatalogs

{ "version": "0", "id": "2617428d-715f-edef-70b8-d210da0317a0", "detail-type": "Glue Data Catalog Table State Change", "source": "aws.glue", "account": "123456789012", "time": "2019-01-16T18:16:01Z", "region": "eu-west-1", "resources": [ "arn:aws:glue:eu-west-1:123456789012:table/d1/t1" ], "detail": { "databaseName": "d1", "changedPartitions": [ "[C.pdf, dir3]", "[D.doc, dir4]" ], "typeOfChange": "BatchCreatePartition", "tableName": "t1" } }

Statusänderung von Datenbanken des AWS Glue-Datenkatalogs

Im folgenden Beispiel lautet der typeofChange CreateTable. Andere mögliche Werte für dieses Feld sind CreateDatabase und UpdateTable.

{ "version": "0", "id": "60e7ddc2-a588-5328-220a-21c060f6c3f4", "detail-type": "Glue Data Catalog Database State Change", "source": "aws.glue", "account": "123456789012", "time": "2019-01-16T18:08:48Z", "region": "eu-west-1", "resources": [ "arn:aws:glue:eu-west-1:123456789012:table/d1/t1" ], "detail": { "databaseName": "d1", "typeOfChange": "CreateTable", "changedTables": [ "t1" ] } }

AWS Ground Station-Ereignisse

Informationen zum BeispielAWS Ground Station-Ereignisse finden Sie unterAutomatisieren vonAWS Ground Stationmit CloudWatch EventsimAWS Ground Station-Benutzerhandbuchaus.

Ereignisse für Amazon GuardDuty

Weitere Informationen zu Amazon GuardDuty Beispielereignissen finden Sie unterÜberwachen von Amazon GuardDuty mit Amazon CloudWatch Events im Benutzerhandbuch für Amazon GuardDuty.

AWS Health-Ereignisse

Im Folgenden ist das Format für die AWS HealthPersonal Health Dashboard(AWS)-Ereignisse aufgeführt. Weitere Informationen finden Sie unter AWS Health Ereignisse mit Amazon CloudWatch Events verwalten im AWS HealthBenutzerhandbuch.

AWS Health-Ereignisformat

{ "version": "0", "id": "7bf73129-1428-4cd3-a780-95db273d1602", "detail-type": "AWS Health Event", "source": "aws.health", "account": "123456789012", "time": "2016-06-05T06:27:57Z", "region": "region", "resources": [], "detail": { "eventArn": "arn:aws:health:region::event/id", "service": "service", "eventTypeCode": "AWS_service_code", "eventTypeCategory": "category", "startTime": "Sun, 05 Jun 2016 05:01:10 GMT", "endTime": "Sun, 05 Jun 2016 05:30:57 GMT", "eventDescription": [{ "language": "lang-code", "latestDescription": "description" }] ... } }
eventTypeCategory

Der Kategorie-Code des Ereignisses. Die möglichen Werte sind issue, accountNotification und scheduledChange.

eventTypeCode

Die eindeutige ID für den Ereignistyp. Beispiele hierfür sind AWS_EC2_INSTANCE_NETWORK_MAINTENANCE_SCHEDULED und AWS_EC2_INSTANCE_REBOOT_MAINTENANCE_SCHEDULED. Ereignisse, die MAINTENANCE_SCHEDULED umfassen, werden in der Regel etwa zwei Wochen vor Beginn der startTime übermittelt.

ID

Die eindeutige ID für das Ereignis.

Service nicht zulässig

Der vom Ereignis betroffene AWS-Service. Beispiele: EC2, S3, REDSHIFT oder RDS.

Elastic Load Balancing-API-Problem

{ "version": "0", "id": "121345678-1234-1234-1234-123456789012", "detail-type": "AWS Health Event", "source": "aws.health", "account": "123456789012", "time": "2016-06-05T06:27:57Z", "region": "ap-southeast-2", "resources": [], "detail": { "eventArn": "arn:aws:health:ap-southeast-2::event/AWS_ELASTICLOADBALANCING_API_ISSUE_90353408594353980", "service": "ELASTICLOADBALANCING", "eventTypeCode": "AWS_ELASTICLOADBALANCING_API_ISSUE", "eventTypeCategory": "issue", "startTime": "Sat, 11 Jun 2016 05:01:10 GMT", "endTime": "Sat, 11 Jun 2016 05:30:57 GMT", "eventDescription": [{ "language": "en_US", "latestDescription": "A description of the event will be provided here" } }

Abnehmende Leistung des Amazon-EC2-Instance-Speicherlaufwerks

{ "version": "0", "id": "121345678-1234-1234-1234-123456789012", "detail-type": "AWS Health Event", "source": "aws.health", "account": "123456789012", "time": "2016-06-05T06:27:57Z", "region": "us-west-2", "resources": [ "i-abcd1111" ], "detail": { "eventArn": "arn:aws:health:us-west-2::event/AWS_EC2_INSTANCE_STORE_DRIVE_PERFORMANCE_DEGRADED_90353408594353980", "service": "EC2", "eventTypeCode": "AWS_EC2_INSTANCE_STORE_DRIVE_PERFORMANCE_DEGRADED", "eventTypeCategory": "issue", "startTime": "Sat, 05 Jun 2016 15:10:09 GMT", "eventDescription": [{ "language": "en_US", "latestDescription": "A description of the event will be provided here" }], "affectedEntities": [{ "entityValue": "i-abcd1111", "tags": { "stage": "prod", "app": "my-app" } }

AWS KMS-Ereignisse

Es folgen Beispiele der Ereignisse für AWS Key Management Service (AWS KMS). Weitere Informationen finden Sie unter AWS KMSEreignisse im AWS Key Management ServiceEntwicklerhandbuch.

KMS-CMK-Rotation

AWS KMS hat automatisch Schlüsselinformationen eines CMK rotiert.

{ "version": "0", "id": "6a7e8feb-b491-4cf7-a9f1-bf3703467718", "detail-type": "KMS CMK Rotation", "source": "aws.kms", "account": "111122223333", "time": "2016-08-25T21:05:33Z", "region": "us-west-2", "resources": [ "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab" ], "detail": { "key-id": "1234abcd-12ab-34cd-56ef-1234567890ab" } }

Ablauf der über KMS importierten Schlüsselinformationen

AWS KMS hat das abgelaufene CMK-Schlüsselmaterial gelöscht.

{ "version": "0", "id": "9da9af57-9253-4406-87cb-7cc400e43465", "detail-type": "KMS Imported Key Material Expiration", "source": "aws.kms", "account": "111122223333", "time": "2016-08-22T20:12:19Z", "region": "us-west-2", "resources": [ "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab" ], "detail": { "key-id": "1234abcd-12ab-34cd-56ef-1234567890ab" } }

Löschen eines KMS-CMK

AWS KMS hat einen geplanten CMK-Löschvorgang abgeschlossen.

{ "version": "0", "id": "e9ce3425-7d22-412a-a699-e7a5fc3fbc9a", "detail-type": "KMS CMK Deletion", "source": "aws.kms", "account": "111122223333", "time": "2016-08-19T03:23:45Z", "region": "us-west-2", "resources": [ "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab" ], "detail": { "key-id": "1234abcd-12ab-34cd-56ef-1234567890ab" } }

Amazon Macie-Ereignisse

Beispiele für Ereignisse, die von Amazon Macie generiert werden, finden Sie unterEreignisschema für Amazon Macie Ergebnisse.

AWS Management Console-Anmeldeereignisse

AWS Management Console-Anmeldereignisse können von CloudWatch Events nur in der Region USA Ost (Nord-Virginia) erkannt werden.

Im Folgenden finden Sie ein Beispiel für ein Anmeldeereignis für die Konsole:

{ "id": "6f87d04b-9f74-4f04-a780-7acf4b0a9b38", "detail-type": "AWS Console Sign In via CloudTrail", "source": "aws.signin", "account": "123456789012", "time": "2016-01-05T18:21:27Z", "region": "us-east-1", "resources": [], "detail": { "eventVersion": "1.02", "userIdentity": { "type": "Root", "principalId": "123456789012", "arn": "arn:aws:iam::123456789012:root", "accountId": "123456789012" }, "eventTime": "2016-01-05T18:21:27Z", "eventSource": "signin.amazonaws.com", "eventName": "ConsoleLogin", "awsRegion": "us-east-1", "sourceIPAddress": "0.0.0.0", "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36", "requestParameters": null, "responseElements": { "ConsoleLogin": "Success" }, "additionalEventData": { "LoginTo": "https://console.aws.amazon.com/console/home?state=hashArgs%23&isauthcode=true", "MobileVersion": "No", "MFAUsed": "No" }, "eventID": "324731c0-64b3-4421-b552-dfc3c27df4f6", "eventType": "AwsConsoleSignIn" } }

AWS OpsWorks-Stacks-Ereignisse

Es folgen Beispiele der AWS OpsWorks-Stack-Ereignisse.

Änderungen des Instance-Zustands bei AWS OpsWorks-Stacks

Kennzeichnet eine Änderung des Zustands einer AWS OpsWorks-Stacks-Instance. Es folgen Instance-Zustände.

  • booting

  • connection_lost

  • online

  • pending

  • rebooting

  • requested

  • running_setup

  • setup_failed

  • shutting_down

  • start_failed

  • stopping

  • stop_failed

  • stopped

  • terminating

  • terminated

{ "version": "0", "id": "dc5fa8df-48f1-2108-b1b9-1fe5ebcf2296", "detail-type": "OpsWorks Instance State Change", "source": "aws.opsworks", "account": "123456789012", "time": "2018-01-25T11:12:23Z", "region": "us-east-1", "resources": [ "arn:aws:opsworks:us-east-1:123456789012:instance/a648d98f-fdd8-4323-952a-a50z3e4z500z" ], "detail": { "initiated_by": "user", "hostname": "testing1", "stack-id": "acd3df16-e859-4598-8414-377b12a902da", "layer-ids": [ "d1a0cb7f-c7e9-4a63-811c-976f0267b2c8" ], "instance-id": "a648d98f-fdd8-4323-952a-a50z3e4z500z", "ec2-instance-id": "i-08b1c2b67aa292276", "status": "requested" } }

Das initiated_by-Feld wird nur ausgefüllt, wenn sich die Instance im Zustand requested, terminating, oder stopping befindet. Das initiated_by-Feld kann einen der folgenden Werte enthalten.

  • user – Ein Benutzer hat die Änderung des Instance-Zustands über die API oder die angefordert AWS Management Console.

  • auto-scaling – Die Änderung des Instance-Zustands wurde von der automatischen Skalierungsfunktion für AWS OpsWorks-Stacks initiiert.

  • auto-healing – Die Änderung des Instance-Zustands wurde von der automatischen Reparaturfunktion für AWS OpsWorks-Stacks initiiert.

Änderungen des Befehlszustands bei AWS OpsWorks-Stacks

Es erfolgte eine Änderung beim Zustand eines AWS OpsWorks-Stacks-Befehls. Es folgen Befehlszustände.

  • expired – Ein Befehls-Timeout.

  • failed – Ein Fehler bei einem allgemeiner Befehl ist aufgetreten.

  • skipped – Ein Befehl wurde übersprungen, da die Instance bei AWS OpsWorks -Stacks einen anderen Zustand als bei Amazon EC2 angenommen hat.

  • successful – Ein Befehl war erfolgreich.

  • superseded – Ein Befehl wurde übersprungen, da andernfalls Konfigurationsänderungen angewendet worden wären, die bereits umgesetzt wurden.

{ "version": "0", "id": "96c778b6-a40e-c8c1-aafc-c9852a3a7b52", "detail-type": "OpsWorks Command State Change", "source": "aws.opsworks", "account": "123456789012", "time": "2018-01-26T08:54:40Z", "region": "us-east-1", "resources": [ "arn:aws:opsworks:us-east-1:123456789012:instance/a648d98f-fdd8-4323-952a-a50a3e4e500f" ], "detail": { "command-id": "acc9f4f3-a3ec-4fab-b70f-c7d04e71e3ec", "instance-id": "a648d98f-fdd8-4323-952a-a50a3e4e500f", "type": "setup", "status": "successful" } }

Änderungen des Bereitstellungszustands bei AWS OpsWorks-Stacks

Es erfolgte eine Änderung beim Zustand einer AWS OpsWorks-Stacks-Bereitstellung. Es folgen Bereitstellungszustände.

  • running

  • successful

  • failed

{ "version": "0", "id": "b8230afa-60c7-f43f-b632-841c1cfb22ff", "detail-type": "OpsWorks Deployment State Change", "source": "aws.opsworks", "account": "123456789012", "time": "2018-01-25T11:15:48Z", "region": "us-east-1", "resources": [ "arn:aws:opsworks:us-east-1:123456789012:instance/a648d98f-fdd8-4323-952a-a50a3e4e500f" ], "detail": { "duration": 16, "stack-id": "acd3df16-e859-4598-8414-377b12a902da", "instance-ids": [ "a648d98f-fdd8-4323-952a-a50a3e4e500f" ], "deployment-id": "606419dc-418e-489c-8531-bff9770fc346", "command": "configure", "status": "successful" } }

Das duration-Feld wird nur ausgefüllt, wenn eine Bereitstellung beendet wurde. Die Zeit wird in Sekunden angegeben.

AWS OpsWorks-Stacks-Warnung

Ein AWS OpsWorks-Stacks-Service-Fehler ist aufgetreten.

{ "version": "0", "id": "f99faa6f-0e27-e398-95bb-8f190806d275", "detail-type": "OpsWorks Alert", "source": "aws.opsworks", "account": "123456789012", "time": "2018-01-20T16:51:29Z", "region": "us-east-1", "resources": [], "detail": { "stack-id": "2f48f2be-ac7d-4dd5-80bb-88375f94db7b", "instance-id": "986efb74-69e8-4c6d-878e-5b77c054cbb0", "type": "InstanceStop", "message": "The shutdown of the instance timed out. Please try stopping it again." } }

SageMaker Events

Weitere Informationen zu SageMaker-Beispielereignissen finden Sie unterAutomatisieren von SageMaker mit Amazon EventBridgeimSageMaker-Entwicklerhandbuch

AWS Security Hub-Ereignisse

Weitere Informationen zu Security Hub-Beispielereignissen finden Sie unterÜberwachungAWS Security Hubmit Amazon CloudWatch EventsimAWS Security Hub-Benutzerhandbuchaus.

AWS Server Migration Service-Ereignisse

Es folgen Beispiele der Ereignisse für AWS Server Migration Service.

Benachrichtigung über gelöschten Replikationsauftrag

{ "version": "0", "id": "5630992d-92cd-439f-f2a8-92c8212aee24", "detail-type": "Server Migration Job State Change", "source": "aws.sms", "account": "123456789012", "time": "2018-02-07T22:30:11Z", "region": "us-west-1", "resources": [ "arn:aws:sms:us-west-1:123456789012:sms-job-21a64348" ], "detail": { "state": "Deleted", "replication-run-id": "N/A", "replication-job-id": "sms-job-21a64348", "version": "1.0" } }

Benachrichtigung über abgeschlossenen Replikationsauftrag

{ "version": "0", "id": "3f9c59cc-f941-522a-be6d-f08e44ff1715", "detail-type": "Server Migration Job State Change", "source": "aws.sms", "account": "123456789012", "time": "2018-02-07T22:54:00Z", "region": "us-west-1", "resources": [ "arn:aws:sms:us-west-1:123456789012:sms-job-2ea64347", "arn:aws:sms:us-west-1:123456789012:sms-job-2ea64347/sms-run-e1a64388" ], "detail": { "state": "Completed", "replication-run-id": "sms-run-e1a64388", "replication-job-id": "sms-job-2ea64347", "ami-id": "ami-746d6314", "version": "1.0" } }

AWS Systems Manager-Ereignisse

Es folgen Beispiele der Ereignisse für AWS Systems Manager. Weitere Informationen finden Sie unterÜberwachen Systems Manager Ereignissen mit Amazon EventBridgeimAWS Systems Manager-Benutzerhandbuchaus.

AWS Systems ManagerAutomatisieren von Events

Benachrichtigung über die Änderung des Automatisierungsschrittstatus

{ "version": "0", "id": "eeca120b-a321-433e-9635-dab369006a6b", "detail-type": "EC2 Automation Step Status-change Notification", "source": "aws.ssm", "account": "123456789012", "time": "2016-11-29T19:43:35Z", "region": "us-east-1", "resources": ["arn:aws:ssm:us-east-1:123456789012:automation-execution/333ba70b-2333-48db-b17e-a5e69c6f4d1c", "arn:aws:ssm:us-east-1:123456789012:automation-definition/runcommand1:1"], "detail": { "ExecutionId": "333ba70b-2333-48db-b17e-a5e69c6f4d1c", "Definition": "runcommand1", "DefinitionVersion": 1.0, "Status": "Success", "EndTime": "Nov 29, 2016 7:43:25 PM", "StartTime": "Nov 29, 2016 7:43:23 PM", "Time": 2630.0, "StepName": "runFixedCmds", "Action": "aws:runCommand" } }

Benachrichtigung über die Änderung des Ausführungsstatus

{ "version": "0", "id": "d290ece9-1088-4383-9df6-cd5b4ac42b99", "detail-type": "EC2 Automation Execution Status-change Notification", "source": "aws.ssm", "account": "123456789012", "time": "2016-11-29T19:43:35Z", "region": "us-east-1", "resources": ["arn:aws:ssm:us-east-1:123456789012:automation-execution/333ba70b-2333-48db-b17e-a5e69c6f4d1c", "arn:aws:ssm:us-east-1:123456789012:automation-definition/runcommand1:1"], "detail": { "ExecutionId": "333ba70b-2333-48db-b17e-a5e69c6f4d1c", "Definition": "runcommand1", "DefinitionVersion": 1.0, "Status": "Success", "StartTime": "Nov 29, 2016 7:43:20 PM", "EndTime": "Nov 29, 2016 7:43:26 PM", "Time": 5753.0, "ExecutedBy": "arn:aws:iam::123456789012:user/userName" } }

AWS Systems ManagerKalenderereignisse ändern

Es folgen Beispiele der Ereignisse fürAWS Systems ManagerKalender ändern.

Anmerkung

Statusänderungen für Kalender, die von anderen freigegeben werdenAWS-Konten werden derzeit nicht unterstützt.

Kalender OFFEN

{ "version": "0", "id": "47a3f03a-f30d-1011-ac9a-du3bdEXAMPLE", "detail-type": "Calendar State Change", "source": "aws.ssm", "account": "111222333444", "time": "2020-09-19T18:00:07Z", "region": "us-east-2", "resources": [ "arn:aws:ssm:us-east-2:111222333444:document/MyCalendar" ], "detail": { "state": "OPEN", "atTime": "2020-09-19T18:00:07Z", "nextTransitionTime": "2020-10-11T18:00:07Z" } }

Kalender GESCHLOSSEN

{ "version": "0", "id": "f30df03a-1011-ac9a-47a3-f761eEXAMPLE", "detail-type": "Calendar State Change", "source": "aws.ssm", "account": "111222333444", "time": "2020-09-17T21:40:02Z", "region": "us-east-2", "resources": [ "arn:aws:ssm:us-east-2:111222333444:document/MyCalendar" ], "detail": { "state": "CLOSED", "atTime": "2020-08-17T21:40:00Z", "nextTransitionTime": "2020-09-19T18:00:07Z" } }

AWS Systems ManagerCompliance-Ereignisse

Es folgen Beispiele der Ereignisse für AWS Systems Manager Compliance.

Zuordnung regelkonform

{ "version": "0", "id": "01234567-0123-0123-0123-012345678901", "detail-type": "Configuration Compliance State Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-07-17T19:03:26Z", "region": "us-west-1", "resources": [ "arn:aws:ssm:us-west-1:461348341421:managed-instance/i-01234567890abcdef" ], "detail": { "last-runtime": "2017-01-01T10:10:10Z", "compliance-status": "compliant", "resource-type": "managed-instance", "resource-id": "i-01234567890abcdef", "compliance-type": "Association" } }

Zuordnung nicht regelkonform

{ "version": "0", "id": "01234567-0123-0123-0123-012345678901", "detail-type": "Configuration Compliance State Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-07-17T19:02:31Z", "region": "us-west-1", "resources": [ "arn:aws:ssm:us-west-1:461348341421:managed-instance/i-01234567890abcdef" ], "detail": { "last-runtime": "2017-01-01T10:10:10Z", "compliance-status": "non_compliant", "resource-type": "managed-instance", "resource-id": "i-01234567890abcdef", "compliance-type": "Association" } }

Patch regelkonform

{ "version": "0", "id": "01234567-0123-0123-0123-012345678901", "detail-type": "Configuration Compliance State Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-07-17T19:03:26Z", "region": "us-west-1", "resources": [ "arn:aws:ssm:us-west-1:461348341421:managed-instance/i-01234567890abcdef" ], "detail": { "resource-type": "managed-instance", "resource-id": "i-01234567890abcdef", "compliance-status": "compliant", "compliance-type": "Patch", "patch-baseline-id": "PB789", "severity": "critical" } }

Patch nicht regelkonform

{ "version": "0", "id": "01234567-0123-0123-0123-012345678901", "detail-type": "Configuration Compliance State Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-07-17T19:02:31Z", "region": "us-west-1", "resources": [ "arn:aws:ssm:us-west-1:461348341421:managed-instance/i-01234567890abcdef" ], "detail": { "resource-type": "managed-instance", "resource-id": "i-01234567890abcdef", "compliance-status": "non_compliant", "compliance-type": "Patch", "patch-baseline-id": "PB789", "severity": "critical" } }

AWS Systems Manager-Wartungsfenster-Ereignisse

Es folgen Beispiele für Ereignisse für Systems Manager-Wartungsfenster.

Registrieren eines Ziels

Der andere gültige Statuswert ist DEREGISTERED.

{ "version":"0", "id":"01234567-0123-0123-0123-0123456789ab", "detail-type":"Maintenance Window Target Registration Notification", "source":"aws.ssm", "account":"012345678901", "time":"2016-11-16T00:58:37Z", "region":"us-east-1", "resources":[ "arn:aws:ssm:us-west-2:001312665065:maintenancewindow/mw-0ed7251d3fcf6e0c2", "arn:aws:ssm:us-west-2:001312665065:windowtarget/e7265f13-3cc5-4f2f-97a9-7d3ca86c32a6" ], "detail":{ "window-target-id":"e7265f13-3cc5-4f2f-97a9-7d3ca86c32a6", "window-id":"mw-0ed7251d3fcf6e0c2", "status":"REGISTERED" } }

Fensterausführungstyp

Die anderen gültigen Statuswerte sindPENDING,IN_PROGRESS,SUCCESS,FAILED,TIMED_OUT, undSKIPPED_OVERLAPPINGaus.

{ "version":"0", "id":"01234567-0123-0123-0123-0123456789ab", "detail-type":"Maintenance Window Execution State-change Notification", "source":"aws.ssm", "account":"012345678901", "time":"2016-11-16T01:00:57Z", "region":"us-east-1", "resources":[ "arn:aws:ssm:us-west-2:0123456789ab:maintenancewindow/mw-123456789012345678" ], "detail":{ "start-time":"2016-11-16T01:00:56.427Z", "end-time":"2016-11-16T01:00:57.070Z", "window-id":"mw-0ed7251d3fcf6e0c2", "window-execution-id":"b60fb56e-776c-4e5c-84ee-123456789012", "status":"TIMED_OUT" } }

Typ der Aufgabenausführung

Die anderen gültigen Statuswerte sindIN_PROGRESS,SUCCESS,FAILED, undTIMED_OUTaus.

{ "version":"0", "id":"01234567-0123-0123-0123-0123456789ab", "detail-type":"Maintenance Window Task Execution State-change Notification", "source":"aws.ssm", "account":"012345678901", "time":"2016-11-16T01:00:56Z", "region":"us-east-1", "resources":[ "arn:aws:ssm:us-west-2:0123456789ab:maintenancewindow/mw-123456789012345678" ], "detail":{ "start-time":"2016-11-16T01:00:56.759Z", "task-execution-id":"6417e808-7f35-4d1a-843f-123456789012", "end-time":"2016-11-16T01:00:56.847Z", "window-id":"mw-0ed7251d3fcf6e0c2", "window-execution-id":"b60fb56e-776c-4e5c-84ee-123456789012", "status":"TIMED_OUT" } }

Aufgabenziel verarbeitet

Die anderen gültigen Statuswerte sindIN_PROGRESS,SUCCESS,FAILED, undTIMED_OUTaus.

{ "version":"0", "id":"01234567-0123-0123-0123-0123456789ab", "detail-type":"Maintenance Window Task Target Invocation State-change Notification", "source":"aws.ssm", "account":"012345678901", "time":"2016-11-16T01:00:57Z", "region":"us-east-1", "resources":[ "arn:aws:ssm:us-west-2:0123456789ab:maintenancewindow/mw-123456789012345678" ], "detail":{ "start-time":"2016-11-16T01:00:56.427Z", "end-time":"2016-11-16T01:00:57.070Z", "window-id":"mw-0ed7251d3fcf6e0c2", "window-execution-id":"b60fb56e-776c-4e5c-84ee-123456789012", "task-execution-id":"6417e808-7f35-4d1a-843f-123456789012", "window-target-id":"e7265f13-3cc5-4f2f-97a9-123456789012", "status":"TIMED_OUT", "owner-information":"Owner" } }

Fensterstatusänderung

Die gültigen Werte sind ENABLED und DISABLED.

{ "version":"0", "id":"01234567-0123-0123-0123-0123456789ab", "detail-type":"Maintenance Window State-change Notification", "source":"aws.ssm", "account":"012345678901", "time":"2016-11-16T00:58:37Z", "region":"us-east-1", "resources":[ "arn:aws:ssm:us-west-2:0123456789ab:maintenancewindow/mw-123456789012345678" ], "detail":{ "window-id":"mw-123456789012", "status":"DISABLED" } }

AWS Systems Manager-Parameter-Speicherereignisse

Es folgen Beispiele der Ereignisse für Amazon EC2 Systems Manager (SSM) Parameter Store.

Create Parameter (Parameter erstellen)

{ "version": "0", "id": "6a7e4feb-b491-4cf7-a9f1-bf3703497718", "detail-type": "Parameter Store Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-05-22T16:43:48Z", "region": "us-east-1", "resources": [ "arn:aws:ssm:us-east-1:123456789012:parameter/foo" ], "detail": { "operation": "Create", "name": "foo", "type": "String", "description": "Sample Parameter" } }

Update Parameter (Parameter aktualisieren)

{ "version": "0", "id": "9547ef2d-3b7e-4057-b6cb-5fdf09ee7c8f", "detail-type": "Parameter Store Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-05-22T16:44:48Z", "region": "us-east-1", "resources": [ "arn:aws:ssm:us-east-1:123456789012:parameter/foo" ], "detail": { "operation": "Update", "name": "foo", "type": "String", "description": "Sample Parameter" } }

DeleteParameter (Parameter löschen)

{ "version": "0", "id": "80e9b391-6a9b-413c-839a-453b528053af", "detail-type": "Parameter Store Change", "source": "aws.ssm", "account": "123456789012", "time": "2017-05-22T16:45:48Z", "region": "us-east-1", "resources": [ "arn:aws:ssm:us-east-1:123456789012:parameter/foo" ], "detail": { "operation": "Delete", "name": "foo", "type": "String", "description": "Sample Parameter" } }

AWS Systems ManagerRun Command-Ereignisse

Benachrichtigung über die Änderung des Status von Run Command

{ "version": "0", "id": "51c0891d-0e34-45b1-83d6-95db273d1602", "detail-type": "EC2 Command Status-change Notification", "source": "aws.ssm", "account": "123456789012", "time": "2016-07-10T21:51:32Z", "region": "us-east-1", "resources": ["arn:aws:ec2:us-east-1:123456789012:instance/i-abcd1111"], "detail": { "command-id": "e8d3c0e4-71f7-4491-898f-c9b35bee5f3b", "document-name": "AWS-RunPowerShellScript", "expire-after": "2016-07-14T22:01:30.049Z", "parameters": { "executionTimeout": ["3600"], "commands": ["date"] }, "requested-date-time": "2016-07-10T21:51:30.049Z", "status": "Success" } }

Benachrichtigung über die Änderung des Aufrufstatus von Run Command

{ "version": "0", "id": "4780e1b8-f56b-4de5-95f2-95db273d1602", "detail-type": "EC2 Command Invocation Status-change Notification", "source": "aws.ssm", "account": "123456789012", "time": "2016-07-10T21:51:32Z", "region": "us-east-1", "resources": ["arn:aws:ec2:us-east-1:123456789012:instance/i-abcd1111"], "detail": { "command-id": "e8d3c0e4-71f7-4491-898f-c9b35bee5f3b", "document-name": "AWS-RunPowerShellScript", "instance-id": "i-9bb89e2b", "requested-date-time": "2016-07-10T21:51:30.049Z", "status": "Success" } }

AWS Systems Manager-Statusänderungsereignisse

Änderung des Zuordnungsstatus in State Manager

{ "version":"0", "id":"db839caf-6f6c-40af-9a48-25b2ae2b7774", "detail-type":"EC2 State Manager Association State Change", "source":"aws.ssm", "account":"123456789012", "time":"2017-05-16T23:01:10Z", "region":"us-west-1", "resources":[ "arn:aws:ssm:us-west-1::document/AWS-RunPowerShellScript" ], "detail":{ "association-id":"6e37940a-23ba-4ab0-9b96-5d0a1a05464f", "document-name":"AWS-RunPowerShellScript", "association-version":"1", "document-version":"Optional.empty", "targets":"[{\"key\":\"InstanceIds\",\"values\":[\"i-12345678\"]}]", "creation-date":"2017-02-13T17:22:54.458Z", "last-successful-execution-date":"2017-05-16T23:00:01Z", "last-execution-date":"2017-05-16T23:00:01Z", "last-updated-date":"2017-02-13T17:22:54.458Z", "status":"Success", "association-status-aggregated-count":"{\"Success\":1}", "schedule-expression":"cron(0 */30 * * * ? *)", "association-cwe-version":"1.0" } }

Statusänderung der Instance-Zuordnung in State Manager

{ "version":"0", "id":"6a7e8feb-b491-4cf7-a9f1-bf3703467718", "detail-type":"EC2 State Manager Instance Association State Change", "source":"aws.ssm", "account":"123456789012", "time":"2017-02-23T15:23:48Z", "region":"us-east-1", "resources":[ "arn:aws:ec2:us-east-1:123456789012:instance/i-12345678", "arn:aws:ssm:us-east-1:123456789012:document/my-custom-document" ], "detail":{ "association-id":"34fcb7e0-9a14-4984-9989-0e04e3f60bd8", "instance-id":"i-12345678", "document-name":"my-custom-document", "document-version":"1", "targets":"[{\"key\":\"instanceids\",\"values\":[\"i-12345678\"]}]", "creation-date":"2017-02-23T15:23:48Z", "last-successful-execution-date":"2017-02-23T16:23:48Z", "last-execution-date":"2017-02-23T16:23:48Z", "status":"Success", "detailed-status":"", "error-code":"testErrorCode", "execution-summary":"testExecutionSummary", "output-url":"sampleurl", "instance-association-cwe-version":"1" } }

AWS Step Functions-Ereignisse

Informationen zu Step Functions Beispielereignissen finden Sie unterBeispiele für Step Functions EventsimAWS Step FunctionsEntwicklerhandbuchaus.

Tag-Änderungsereignisse auf AWS-Ressourcen

Es folgt ein Beispiel für ein Tag-Ereignis.

{ "version": "0", "id": "ffd8a6fe-32f8-ef66-c85c-111111111111", "detail-type": "Tag Change on Resource", "source": "aws.tag", "account": "123456789012", "time": "2018-09-18T20:41:06Z", "region": "us-east-1", "resources": [ "arn:aws:ec2:us-east-1:123456789012:instance/i-0000000aaaaaaaaaa" ], "detail": { "changed-tag-keys": [ "key2", "key3" ], "service": "ec2", "resource-type": "instance", "version": 5, "tags": { "key4": "value4", "key1": "value1", "key2": "value2" } } }

AWS Trusted Advisor-Ereignisse

Es folgen Beispiele der Ereignisse für AWS Trusted Advisor. Weitere Informationen finden Sie unterÜberwachungTrusted AdvisorÜberprüfen von Ergebnissen mit Amazon CloudWatch EventsimAWS Support-Benutzerhandbuchaus.

Low Utilization Amazon EC2 Instances

{ "version": "0", "id": "1234abcd-ab12-123a-123a-1234567890ab", "detail-type": "Trusted Advisor Check Item Refresh Notification", "source": "aws.trustedadvisor", "account": "123456789012", "time": "2018-01-12T20:07:49Z", "region": "us-east-2", "resources": [], "detail": { "check-name": "Low Utilization Amazon EC2 Instances", "check-item-detail": { "Day 1": "0.1% 0.00MB", "Day 2": "0.1% 0.00MB", "Day 3": "0.1% 0.00MB", "Region/AZ": "ca-central-1a", "Estimated Monthly Savings": "$9.22", "14-Day Average CPU Utilization": "0.1%", "Day 14": "0.1% 0.00MB", "Day 13": "0.1% 0.00MB", "Day 12": "0.1% 0.00MB", "Day 11": "0.1% 0.00MB", "Day 10": "0.1% 0.00MB", "14-Day Average Network I/O": "0.00MB", "Number of Days Low Utilization": "14 days", "Instance Type": "t2.micro", "Instance ID": "i-01234567890abcdef", "Day 8": "0.1% 0.00MB", "Instance Name": null, "Day 9": "0.1% 0.00MB", "Day 4": "0.1% 0.00MB", "Day 5": "0.1% 0.00MB", "Day 6": "0.1% 0.00MB", "Day 7": "0.1% 0.00MB" }, "status": "WARN", "resource_id": "arn:aws:ec2:ca-central-1:123456789012:instance/i-01234567890abcdef", "uuid": "aa12345f-55c7-498e-b7ac-123456789012" } }

Load Balancer Optimization

{ "version": "0", "id": "1234abcd-ab12-123a-123a-1234567890ab", "detail-type": "Trusted Advisor Check Item Refresh Notification", "source": "aws.trustedadvisor", "account": "123456789012", "time": "2018-01-12T20:07:03Z", "region": "us-east-2", "resources": [], "detail": { "check-name": "Load Balancer Optimization ", "check-item-detail": { "Instances in Zone a": "1", "Status": "Yellow", "Instances in Zone b": "0", "# of Zones": "2", "Region": "eu-central-1", "Load Balancer Name": "my-load-balance", "Instances in Zone e": null, "Instances in Zone c": null, "Reason": "Single AZ", "Instances in Zone d": null }, "status": "WARN", "resource_id": "arn:aws:elasticloadbalancing:eu-central-1:123456789012:loadbalancer/my-load-balancer", "uuid": "aa12345f-55c7-498e-b7ac-123456789012" } }

Exposed Access Keys

{ "version": "0", "id": "1234abcd-ab12-123a-123a-1234567890ab", "detail-type": "Trusted Advisor Check Item Refresh Notification", "source": "aws.trustedadvisor", "account": "123456789012", "time": "2018-01-12T19:38:24Z", "region": "us-east-1", "resources": [], "detail": { "check-name": "Exposed Access Keys", "check-item-detail": { "Case ID": "12345678-1234-1234-abcd-1234567890ab", "Usage (USD per Day)": "0", "User Name (IAM or Root)": "my-username", "Deadline": "1440453299248", "Access Key ID": "AKIAIOSFODNN7EXAMPLE", "Time Updated": "1440021299248", "Fraud Type": "Exposed", "Location": "www.example.com" }, "status": "ERROR", "resource_id": "", "uuid": "aa12345f-55c7-498e-b7ac-123456789012" } }

WorkSpaces-Ereignisse

Weitere Informationen zu den WorlSpaces-Ereignissen finden Sie unter Überwachen Ihrer WorkSpaces mithilfe von CloudWatch Eventsim Amazon WorkSpaces Administration Guide.

Über CloudTrail übermittelte Ereignisse

Sie können CloudWatch Events auch mit Services verwenden, die keine Ereignisse ausgeben und auf dieser Seite nicht aufgelistet werden. AWS CloudTrail ist ein Service, der Ereignisse wie z. B. AWS-API-Aufrufe automatisch aufzeichnet. Sie können CloudWatch Events-Regeln erstellen, die durch die von CloudTrail erfassten Informationen ausgelöst werden. Weitere Informationen zu CloudTrail finden Sie unter Was ist AWS CloudTrail?. Weitere Informationen zum Erstellen einer CloudWatch Events-Regel, die CloudTrail verwendet, finden Sie unterErstellen einer CloudWatch Events-Regel, die bei einem AWS API-Aufruf mit AWS CloudTrail ausgelöst wirdaus.

Alle über AWS API Call via CloudTrail bereitgestellten Ereignisse weisen für CloudTrail den Wert detail-type auf.

Einige Vorkommnisse in AWS können sowohl vom Service selbst als auch von CloudTrail an CloudWatch Events gemeldet werden, wobei die Benachrichtigung auf unterschiedliche Weise erfolgt. Beispielsweise generiert ein Amazon EC2-API-Aufruf, der eine Instance startet oder beendet, Ereignisse, die in CloudWatch Events über CloudTrail bereitgestellt werden. Dagegen stellen Änderungen des Amazon EC2-Instance-Status (beispielsweise von „wird ausgeführt“ in „wird beendet“) CloudWatch-Events dar.

Es folgt ein Beispiel für ein mittels CloudTrail übermitteltes Ereignis. Das Ereignis wurde durch einen AWS-API-Aufruf zum Erzeugen eines Buckets in Amazon S3 generiert.

{ "version": "0", "id": "36eb8523-97d0-4518-b33d-ee3579ff19f0", "detail-type": "AWS API Call via CloudTrail", "source": "aws.s3", "account": "123456789012", "time": "2016-02-20T01:09:13Z", "region": "us-east-1", "resources": [], "detail": { "eventVersion": "1.03", "userIdentity": { "type": "Root", "principalId": "123456789012", "arn": "arn:aws:iam::123456789012:root", "accountId": "123456789012", "sessionContext": { "attributes": { "mfaAuthenticated": "false", "creationDate": "2016-02-20T01:05:59Z" } } }, "eventTime": "2016-02-20T01:09:13Z", "eventSource": "s3.amazonaws.com", "eventName": "CreateBucket", "awsRegion": "us-east-1", "sourceIPAddress": "100.100.100.100", "userAgent": "[S3Console/0.4]", "requestParameters": { "bucketName": "bucket-test-iad" }, "responseElements": null, "requestID": "9D767BCC3B4E7487", "eventID": "24ba271e-d595-4e66-a7fd-9c16cbf8abae", "eventType": "AwsApiCall" } }

AWS-API-Aufrufereignisse, die größer als 256 KB sind, werden nicht unterstützt. Weitere Informationen zu den API-Aufrufen, die Sie als Trigger für Regeln verwenden können, finden Sie unter Services Supported by CloudTrail Event History.