Which approach meets these requirements with the LEAST amount of operational overhead?

A company is building a hybrid solution between its existing on-premises systems and a new backend in AWS. The company has a management application to monitor the state of its current IT infrastructure and automate responses to issues. The company wants to incorporate the status of its consumed AWS services into the application. The application uses an HTTPS endpoint to receive updates.

Which approach meets these requirements with the LEAST amount of operational overhead?
A . Configure AWS Systems Manager OpsCenter to ingest operational events from the on-premises systems Retire the on-premises management application and adopt OpsCenter as the hub
B . Configure Amazon EventBridge (Amazon CloudWatch Events) to detect and react to changes for AWS Health events from the AWS Personal Health Dashboard Configure the EventBridge (CloudWatch Events) event to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic and subscribe the topic to the HTTPS endpoint of the management application
C . Modify the on-premises management application to call the AWS Health API to poll for status events of AWS services.
D . Configure Amazon EventBridge (Amazon CloudWatch Events) to detect and react to changes for AWS Health events from the AWS Service Health Dashboard Configure the EventBridge (CloudWatch Events) event to publish a message to an Amazon Simple
Notification Service (Amazon SNS) topic and subscribe the topic to an HTTPS endpoint for the management application with a topic filter corresponding to the services being used

View Answer

Answer: B

Explanation:

This approach satisfies the requirements with minimal operational overhead, as it directly leverages AWS’s services to monitor the status of AWS resources and push updates to existing HTTPS endpoints via SNS topics. This allows companies to seamlessly integrate their AWS service status into existing management applications without the need to make large-scale changes to existing infrastructure or adopt new management tools such as OpsCenter, which can introduce more learning curves and operational burdens.

Option A requires retiring existing management applications and adopting OpsCenter, which increases operational overhead and detriments the continuity of existing monitoring processes. Option C requires modifying the existing management application to poll the AWS Health API, which increases development effort and possible latency. Option D is similar to B, but mentions the AWS Service Health Panel more specifically, while in reality, the Personal Health Panel provides more customized health event information that is better suited for this use case.