What should the DevOps Engineer do to create notifications when issues are discovered?
Implement AWS CloudWatch Logs for CodePipeline and CodeDeploy, create an AWS Config rule to evaluate code deployment issues, and create an Amazon SNS topic to notify stakeholders of deployment issues.
Implement AWS CloudWatch Events for CodePipeline and CodeDeploy, create an AWS Lambda function to evaluate code deployment issues, and create an Amazon SNS topic to notify stakeholders of deployment issues.
Implement AWS CloudTrail to record CodePipeline and CodeDeploy API call information, create an AWS Lambda function to evaluate code deployment issues, and create an Amazon SNS topic to notify stakeholders of deployment issues.
Implement AWS CloudWatch Events for CodePipeline and CodeDeploy, create an Amazon Inspector assessment target to evaluate code deployment issues, and create an Amazon SNS topic to notify stakeholders of deployment issues.
Explanations:
AWS Config is not designed to evaluate code deployment issues, and CloudWatch Logs are more suited for logging application output, not directly for CodeDeploy failures.
AWS CloudWatch Events can capture events from CodePipeline and CodeDeploy. A Lambda function can process events, evaluate deployment issues, and trigger an SNS notification, which is an efficient way to handle deployment monitoring and notifications.
AWS CloudTrail logs API calls, but it doesn’t provide real-time event monitoring or evaluation of deployment success/failure, which is crucial for fast issue resolution in CodeDeploy.
Amazon Inspector is used for security assessments, not for evaluating deployment issues in CodeDeploy. AWS CloudWatch Events is the better tool for capturing deployment events.
I plot that the answer is:
Implement AWS CloudWatch Events for CodePipeline and CodeDeploy, create an AWS Lambda function to evaluate code deployment issues, and create an Amazon SNS topic to notify stakeholders of deployment issues.