Your team has created a new deployment in AWS CodeDeploy service. It automates the deployments for a new Node.js application to Amazon EC2 instances. In order to pass a notification to a Slack channel whenever deployments fail, a DevOps engineer configured a CloudWatch Event rule as follows:

Answer options:

A.Replace the Lambda function with an SNS topic as the target of the CloudWatch Event rule. Create an HTTP endpoint to subscribe to the topic.
B.Remove the detail-type in the rule in order to capture all CodeDeploy events. Add the logic in the Lambda function to determine the deployment failures and send notifications accordingly.
C.Modify the detail-type to be "CodeDeploy Deployment State-change Notification” in the CloudWatch Event rule.
D.Make sure that the Lambda function has an API gateway to allow the incoming API requests from events.amazonaws.com.

Correct Answer – C
In the CloudWatch Event rule, the detail-type is incorrect as it should check the state change of CodeDeploy deployments instead of instances. As the Event rule cannot find the deployment failures, the Lambda function is not triggered and no notifications are sent to the Slack channel. To fix the problem, the detail-type needs to be modified. References can be found in https://docs.aws.amazon.com/codedeploy/latest/userguide/monitoring-cloudwatch-events.html.
Option A is incorrect: Because there is no need to replace the Lambda function with an SNS topic. The event pattern in the CloudWatch Event rule should be modified.
Option B is incorrect: It is improper to match all CodeDeploy events since only the deployment failure events are required.
Option C is CORRECT: The below event pattern should be configured:
{
"source": [
"aws.codedeploy"
],
"detail-type": [
"CodeDeploy Deployment State-change Notification"
],
"detail": {
"state": [
"FAILURE"
]
}
}
Option D is incorrect: In this scenario, the Lambda function does not need an API gateway in order to be invoked by the CloudWatch Event rule.