Elemental MediaPackage v2 EventBridge Events

Based on the available information, there is no specific mention of MediaPackage v2 emitting events via EventBridge. The sources primarily discuss AWS Elemental MediaPackage (which appears to be v1) and its integration with Amazon CloudWatch Events (now known as Amazon EventBridge).

For MediaPackage v1, it is clear that it integrates with CloudWatch Events/EventBridge to notify users of certain events affecting channels and endpoints. These events include input notification events, key provider notification events, and harvest job notification events. MediaPackage v1 emits these events on a best effort basis.

The events from MediaPackage v1 can be collected and routed to various targets such as AWS Lambda functions, Amazon SNS topics, Amazon SQS queues, and Amazon Kinesis Data Streams. This allows for automation and response to system events in near real-time.

However, without specific information about MediaPackage v2, I cannot confirm whether it emits events via EventBridge in the same way as v1. If you require information about MediaPackage v2's event capabilities, it would be best to consult the most recent AWS documentation or contact AWS support directly for the most up-to-date information.
Sources
AWS Elemental MediaPackage events - AWS Elemental MediaPackage
Monitoring AWS Elemental MediaPackage with CloudWatch Events - AWS Elemental MediaPackage
Creating event notifications - AWS Elemental MediaPackage

You will get many relevant events logged If you create a new CloudWatch Log Group and corresponding Rule to foward events to that log group.

1. Create a log group like "/aws/events/mpv2'
2. Create a new EventBridge Rule (CloudWatch Rule) with the event pattern like:

{
  "source": ["aws.mediapackagev2"]
}

This will forward all events such as CloudTrail api logs into the specified log group, including the creation of harvest jobs against v2 channels:

{
detail.eventName	: CreateHarvestJob
detail.eventSource : mediapackagev2.amazonaws.com
}

MediaPackage v2 harvest jobs do not emit events upon completion today. However: you could build a Lambda or step function which triggers off the CreateHarvestJob event (above) and periodically runs the boto3 equivalent of "aws mediapackagev2 list-harvest-jobs --channel-group-name groupnamehere" to query harvest job status. When a Status value progresses past "IN_PROGRESS" to either 'COMPLETED' or 'FAILED' the result could be pushed to SNS, to CloudWatch or to some other target.