- Newest
- Most votes
- Most comments
Hi,
I would suggest that you replace the direct trigger from EventBridge's event to RedShift procedure by an indirect one. You should create a Lambda that you attach to the event an this Lambda should launch the procedure.
This indirect trigger will give you all the flexibity that you need to log the event in CloudWatch, raises SNS notifications, etc.
Best,
Didier
I'd recommend to start debugging based on this page first https://docs.aws.amazon.com/scheduler/latest/UserGuide/monitoring-overview.html. If you are still unable to make progress, know that EventBridge schedule in the end essentially just calls an API. You can look into making the call directly with the same IAM role to see if the call passes or not. If it does, look into if the IAM trust policies are setup correctly. If you are at lost and need further assistance, reachout to AWS support who can work with internal tooling to help drive this to resolution.
Relevant content
- asked 5 years ago
- asked 9 months ago
- asked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago
I would but the architecture is built around EventBridge and the other calls are there. So creating a new way would require too much overhaul of the system