New serverless pattern - eventbridge-scheduler-ai-agent-trigger#2992
Open
ras-al-jil wants to merge 1 commit intoaws-samples:mainfrom
Open
Conversation
ellisms
requested changes
Apr 14, 2026
Contributor
ellisms
left a comment
ellisms
left a comment
There was a problem hiding this comment.
Hi @ras-al-jil - thank you for your submission. Requesting a few changes.
|
|
||
| ## Testing | ||
|
|
||
| 1. Invoke the orchestrator Lambda manually: |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. Invoke the orchestrator Lambda manually: | |
| 1. Replace `<prefix>` with the prefix chosen during deployment and invoke the orchestrator Lambda function manually: |
| @@ -0,0 +1,89 @@ | |||
| # Amazon EventBridge Scheduler to Amazon Bedrock AI Agent | |||
|
|
|||
| This pattern demonstrates how to trigger an Amazon Bedrock AI Agent on a recurring schedule using Amazon EventBridge Scheduler. An orchestrator Lambda function, invoked by the scheduler, sends a task payload to the Bedrock Agent, which processes the input, generates an execution summary, and persists the result to a DynamoDB table via an action group Lambda. | |||
Contributor
There was a problem hiding this comment.
Suggested change
| This pattern demonstrates how to trigger an Amazon Bedrock AI Agent on a recurring schedule using Amazon EventBridge Scheduler. An orchestrator Lambda function, invoked by the scheduler, sends a task payload to the Bedrock Agent, which processes the input, generates an execution summary, and persists the result to a DynamoDB table via an action group Lambda. | |
| This pattern demonstrates how to trigger an Amazon Bedrock AI Agent on a recurring schedule using Amazon EventBridge Scheduler. An orchestrator AWS Lambda function, invoked by the scheduler, sends a task payload to the Bedrock Agent, which processes the input, generates an execution summary, and persists the result to a Amazon DynamoDB table via an action group Lambda. |
| retention_in_days = var.log_retention_days | ||
| } | ||
|
|
||
| resource "aws_lambda_function" "action_group" { |
Contributor
There was a problem hiding this comment.
I think there is value in not pre-zipping the Lambda code and having TF do this via the archive_file resource type. Recommend including the raw python code and adding the archive_file resource as input to this resource.
| retention_in_days = var.log_retention_days | ||
| } | ||
|
|
||
| resource "aws_lambda_function" "orchestrator" { |
Contributor
There was a problem hiding this comment.
I think there is value in not pre-zipping the Lambda code and having TF do this via the archive_file resource type. Recommend including the raw python code and adding the archive_file resource as input to this resource.
|
|
||
| 1. Destroy the stack: | ||
| ``` | ||
| terraform destroy -auto-approve |
Contributor
There was a problem hiding this comment.
Suggested change
| terraform destroy -auto-approve | |
| terraform destroy --auto-approve |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #2993, if available:
Description of changes:
This pattern demonstrates how to trigger an Amazon Bedrock AI Agent on a recurring schedule using Amazon EventBridge Scheduler. An orchestrator AWS Lambda function, invoked by the scheduler, sends a task payload to the Bedrock Agent, which processes the input, generates an execution summary, and persists the result to a DynamoDB table via an action group Lambda. The pattern includes retry logic, a dead-letter queue for failed invocations, and least-privilege IAM policies scoped to the agent alias ARN.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.