EventBridge for Amazon Bedrock batch inference is not triggering

Question

I have an issue with Bedrock batch inference. I have a flow that is relying on the event that Bedrock publishes when a job status changes: https://docs.aws.amazon.com/bedrock/latest/userguide/monitoring-eventbridge-how-it-works.html. When my jobs are completed I have a Lambda function that will get the results from S3, parse them and insert the output data in services such as Firehose and Dynamo.

This flow has been working fine for weeks until a couple days ago when **it just stopped working**. The way my event rule is defined in Serverless is:
```
BatchStatusChangeEventRule:
  Type: AWS::Events::Rule
  Properties:
    Name: ${self:custom.service}-batch-status-change
    Description: 'An EventBridge rule that triggers whenever a batch status changes'
    EventPattern:
      source:
        - aws.bedrock
      detail-type:
        - 'Batch Inference Job State Change'
      detail:
        batchJobName:
          - prefix: ${opt:stage}-${self:service}
    State: ENABLED
    Targets:
      - Id: BatchStatusChangeHandlerId
        Arn:
          Fn::GetAtt: [ StatusChangeHandlerLambdaFunction, Arn ]
```

I have tried to debug this with a simpler event rule, where the event pattern is:
```
EventPattern:
  source:
    - aws.bedrock
  detail-type:
    - anything-but:
      - "AWS API Call via CloudTrail"
```

But I get no events there although the Bedrock batches are still running and completing.

This has me run the `status-change-handler` Lambda manually with an event that resembles Bedrock's, and eventually I would run this Lambda on a schedule and check for completed jobs but that defeats the whole point of what the event should do.

Did this happen to anyone else ? Has anyone been able to figure out a solution for this ?
Thanks !

PP · Answer

The service resumed for me on 2025-05-11 at 01:30:00 UTC (according to my logs). I'll keep monitoring it the next couple of days hoping it works normally again !

Jon · Answer

I have been using this EventBridge rule successfully for weeks, but it suddenly stopped working a couple of days ago without any apparent changes. The event rule configuration in Serverless is as follows:

```
      - eventBridge:
          pattern:
            source:
              - aws.bedrock
            detail-type:
              - Batch Inference Job State Change
            detail:
              batchJobName: [{ prefix: 'channel-enhance-job' }]
              status:
                - Completed
          role: qyttEventBridgeInvokeLambdaRole
```
The batch inference job shows as Completed, but no event appears in the logs.

I’ve double-checked the permissions and verified that the role (qyttEventBridgeInvokeLambdaRole) has the necessary permissions to invoke the Lambda function.

Has anyone else encountered this issue recently? Could there have been a change in AWS Bedrock or EventBridge behavior that I missed? Any suggestions would be greatly appreciated

Job terminated:
![Enter image description here](/media/postImages/original/IMWDRD1T2JTxeLWxMTIj_cSA)

No event invocation since 2025-05-06 20:05 Local:
![Enter image description here](/media/postImages/original/IMxtJmV-PVTpGomYeHOZtFuw)

re:Post Agent · Answer

Hello,

It seems you're experiencing an issue with Amazon EventBridge not triggering for Amazon Bedrock batch inference job state changes. Here are some potential reasons and troubleshooting steps you can take:

* Permissions: Verify that your IAM permissions are still correct and haven't been altered. Ensure that EventBridge has the necessary permissions to receive events from Bedrock and trigger your Lambda function.

- Event generation: Confirm that Bedrock is actually generating the events. You can check the Bedrock console or CloudWatch logs to verify if the job status changes are being recorded.

- EventBridge rule configuration: Double-check your EventBridge rule configuration. The rule you've shared looks correct, but it's worth reviewing to ensure all details are accurate, including the prefix for the batch job name.

- CloudWatch metrics: Check CloudWatch metrics for your EventBridge rule to see if it's being triggered at all. 
     - **TriggeredRules** represents the number of rules that have run and matched with any event. You won't see this metric in CloudWatch until a rule is triggered.
     - **Invocations** metric publishes a datapoint when a rule forwards an event to a target. This represents successful and failed invocations. 
     - Amazon EventBridge issues a **FailedInvocations** datapoint when it permanently fails to invoke the target. FailedInvocations indicates problems with the target configuration or issues that arise from inadequate permissions.
 - For more information, refer the following:
   - https://repost.aws/knowledge-center/eventbridge-rules-troubleshoot
   - https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-troubleshooting.html
   - https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-monitoring.html

- Broader event pattern: Testing with a broader event pattern can help determine if you're receiving any Bedrock events. If you're not seeing any events with the broader pattern, it could indicate a more fundamental issue with event delivery from Bedrock to EventBridge.

---

For detailed investigation, we would need to check the resources and the permissions in your account. If you still have queries regarding this, I would request you to reach out to our support team by opening a support case with all the resource details, and we will investigate the issue further.

Thank you for your interest in re:Post community.

EventBridge for Amazon Bedrock batch inference is not triggering

Relevant content