How to push CloudWatch Internet Monitor health events to a third-party target with least effort?

A network engineer needs to monitor internet metrics for an application that is in a VPC. The metrics include user experiences such as health events, latency, and traffic insights. The network engineer sets up Amazon CloudWatch Internet Monitor for the application. The engineer wants to push the internet health events to a third-party target. Which solution will meet these requirements with the LEAST implementation effort?

  1. Create a third-party API endpoint in Amazon EventBridge. Configure internet Monitor to send the events to the third-party API endpoint in EventBridge.
  2. Create a third-party API endpoint in Amazon EventBridge. Create a rule in EventBridge that uses Internet Monitor as the source and the third-party API endpoint in EventBridge as the destination. Source Reference Answer
  3. Create a third-party API endpoint in internet Monitor. Configure Internet Monitor to send the events to an Amazon S3 bucket. Configure an AWS Lambda function to send the events to the third-party API endpoint in Internet Monitor.
  4. Create a third-party API endpoint in Internet Monitor. Configure Internet Monitor to send the events to the third-party API endpoint in Internet Monitor.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests whether you know that Internet Monitor automatically publishes events to EventBridge, so a simple EventBridge rule with an API destination is enough; the trap is confusing EventBridge API destinations with creating endpoints directly inside Internet Monitor.

For the ANS-C01 exam, the least-effort way to push CloudWatch Internet Monitor health events to a third-party target is to use an Amazon EventBridge rule with Internet Monitor as the source. Community consensus strongly supports option B because it leverages native AWS integration rather than custom endpoints or additional services like Lambda.

Choosing D, which incorrectly assumes Internet Monitor can natively send events to a third-party API endpoint. Internet Monitor does not have a built-in third-party endpoint configuration; it emits events to EventBridge, and EventBridge routes them to API destinations.

Community Discussion (3 comments)

youonebe 👍 1 Selected: B
Answer is B, not D
woorkim 👍 1 Selected: B
https://aws.amazon.com/blogs/networking-and-content-delivery/using-amazon-cloudwatch-internet-monitor-for-enhanced-internet-observability/ low-effort solution is to use Amazon EventBridge to create a rule that routes Internet Monitor events to the third-party API endpoint. This approach leverages native AWS integrations and avoids unnecessary complexity.
ArunRav 👍 1 Selected: B
By setting a rule and forwarding the events to the third party endpoint will be least effort required option.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Amazon CloudWatch Internet Monitor automatically publishes health events to Amazon EventBridge. By creating an EventBridge rule with Internet Monitor as the source and a third-party API endpoint as the destination (via EventBridge API destinations), you get a native, serverless, low-effort integration. No custom Lambda, S3 bucket, or direct Internet Monitor endpoint is needed. As one comment [1] notes, this approach leverages native AWS integrations and avoids unnecessary complexity.

Why the Other Options Are Wrong

Option A is wrong because it suggests configuring Internet Monitor to send events directly to an EventBridge API endpoint, but Internet Monitor does not push directly to endpoints; it emits events to EventBridge, which then requires a rule to route them. Option C is unnecessarily complex and incorrectly refers to creating an endpoint in Internet Monitor; using S3 and Lambda adds implementation effort without any benefit. Option D is impossible because Internet Monitor does not support configuring third-party API endpoints directly inside its own service.

Community Comment Notes

The community is unanimous on B (100% votes). One comment [1] provides a helpful AWS blog link about using CloudWatch Internet Monitor for enhanced internet observability, calling EventBridge the low-effort solution. Another comment [2] simply states that setting a rule and forwarding events to a third-party endpoint is the least-effort option. The discussion confirms that EventBridge is the intended integration path for Internet Monitor events.

Official Reference

Exam Strategy

Remember that Internet Monitor automatically publishes events to EventBridge, and EventBridge API destinations are the native way to invoke third-party HTTP endpoints. When a question asks for the 'least implementation effort,' choose the native EventBridge rule over introducing S3, Lambda, or any nonexistent Internet Monitor endpoint configuration.

Related Analysis

A company's AWS infrastructure is spread across more than 50

A-Grade

A company uses transit gateways to route traffic between the

A-Grade

A company has two business units (BUs). The company operates

A-Grade

Practice All ANS-C01 Questions

Access 137 questions with complete answers and detailed explanations.

View Full ANS-C01 Practice Test →

← Back to ANS-C01 Study Guide