- Newest
- Most votes
- Most comments
I'd be happy to help you troubleshoot this issue. Here are a few steps you can take to resolve it:
-
Verify the AWS Batch job's status: Check the status of the job you are trying to schedule. Ensure that the job is in a valid state, such as
VALID
orENABLED
. If the status isINVALID
orDISABLED
, you may need to fix any configuration issues or enable the job. -
Confirm that the job is properly tagged: AWS Batch jobs need to have specific tags to be recognized by Amazon EventBridge. Ensure that the job has a tag with the key
aws:dlm:event-type:batch-job
and a value that matches the value you specified in the EventBridge rule. -
Confirm that the EventBridge rule is correctly set up: Double-check your EventBridge rule configuration. Ensure that the rule is targeting the correct event pattern or schedule expression and that the target is set to AWS Batch. Make sure the rule is active and hasn't expired.
-
Check the Amazon EventBridge event bus: Verify that the event bridge is using the correct event bus or default event bus. Check if the rule and event are visible or if any filtering is in place that may prevent the job from being triggered.
-
Review CloudWatch Logs: If the above steps didn't solve the issue, you can enable CloudWatch logging for your job and check the related logs. This can help you identify any errors or issues that are preventing the job from being scheduled correctly.
@Pedro As shown below Batch Job Queue being showed under AWS service as target in AP-SOUTH-1 region but not showing up in AP-SOUTH-2 region. This is the new region we enabled yesterday
Regards, Rajesh B
Relevant content
- asked 2 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago