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?
The company needs a solution to incorporate the status of its consumed AWS services into an existing on-premises management application that uses an HTTPS endpoint to receive updates. Configuring Amazon EventBridge (Amazon CloudWatch Events) to detect and react to AWS Health events from the AWS Personal Health Dashboard meets these requirements. It can publish messages to an Amazon SNS topic, which can then be subscribed to the HTTPS endpoint of the management application, ensuring minimal operational overhead by leveraging managed AWS services and automated messaging.
The Service Health Dashboard is a good way to view the overall status of each AWS service, but provides little in terms of how the health of those services is impacting your resources. AWS Personal Health Dashboard provides a personalized view of the health of the specific services that are powering your workloads and applications. What’s more, Personal Health Dashboard proactively notifies you when AWS experiences any events that may affect you, helping provide quick visibility and guidance to help you minimize the impact of events in progress, and plan for any scheduled changes, such as AWS hardware maintenance.
AWS Personal Health Dashboard is about the resources you own. AWS Service Health Dashboard is about the status of the AWS services
D - they need only to get data on AWS services they consume, not all services on AWS. so not B, choose D!
D is what is used for all AWS services (not for one particular account). Since AWS Service Health Dashboard is public...it cannot interface with EventBridge. Answer is B since that dashboard is related to services within your account.
AWS Personal Health Dashboard == keyword because only need own Health service with usage the organization other services not is need in this case
https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html why not D (from above link) Currently, you can't use EventBridge to return public events from the Service Health Dashboard. Events from the Service Health Dashboard provide public information about the Regional availability of a service. These events aren't specific to AWS accounts, so they aren't delivered to EventBridge.
https://aws.amazon.com/about-aws/whats-new/2016/12/introducing-aws-personal-health-dashboard/ You can now receive notification and remediation guidance when AWS is experiencing events that may impact you. Available to all AWS customers, AWS Personal Health Dashboard provides a personalized view into the performance and availability of the AWS services you are using, as well as alerts that are automatically triggered by changes in the health of those services.
B) AWS Personal Health Dashboard vs AWS Service Health Dashboard
Setting up Systems Manager for hybrid and multicloud environments https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-managedinstances.html
from chatgpt Option B cannot be the answer because the AWS Health events from the Personal Health Dashboard are intended for personal health monitoring and are not intended to be used as a source of event data for automated operations. Additionally, while the Personal Health Dashboard can be used to monitor the overall health of AWS services and communicate outages, it is not a source of detailed, actionable event data that can be used to integrate with the on-premises management application. For these reasons, Option C, which involves modifying the on-premises management application to call the AWS Health API to poll for status events of AWS services, is the most appropriate solution in this case as it provides a programmatic way for the management application to access detailed, actionable event data about the state of the consumed AWS services.
A. doesn't support on-pr em infra monitoring B. send aws resource health to on-prem monitoring C,D others already discussed
"The application uses an HTTPS endpoint to receive updates." So lazy app will not call AWS Health api, then C is not option. My best guess B also