Which approach meets these requirements with the LEAST amount of operational overhead?
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.
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 (CloudWateh 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.
Modify the on-premises management application to call the AWS Health API to poll for status events of AWS services.
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 (CloudWateh 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.
Explanations:
AWS Systems Manager OpsCenter is primarily designed for managing incidents and operations within AWS environments. It would require significant effort to migrate the existing monitoring solution to OpsCenter, which increases operational overhead, and does not directly integrate with the on-premises system.
EventBridge can react to AWS Health events and send notifications. By publishing these notifications to an SNS topic and subscribing the management application’s HTTPS endpoint, the company can integrate AWS service statuses into its monitoring system with minimal operational overhead. It requires little maintenance once set up.
Polling the AWS Health API from the on-premises management application would require custom coding and additional management overhead. It would also be less efficient than event-driven approaches, as the application would need to periodically check for updates.
Similar to Option B, but this option involves using AWS Service Health Dashboard, which provides status information about AWS regions and services, not tailored to individual customer accounts. It does not provide detailed, personalized event data like the AWS Personal Health Dashboard, making it less relevant for integrating AWS service statuses into a custom application.
I would say the answer is:
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 (CloudWateh 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.