Skip to content

Commit b73f81a

Browse files
committed
pattern updates
1 parent e275fc5 commit b73f81a

File tree

4 files changed

+37
-230
lines changed

4 files changed

+37
-230
lines changed

eventbridge-scheduled-stepfunction-bedrock-kb-sync/eb-scheduled-sfn-bedrock-kb-sync.json

Lines changed: 0 additions & 95 deletions
This file was deleted.
Lines changed: 25 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,39 +1,21 @@
11
{
2-
"authors": [
3-
{
4-
"name": "Shankar Srinivasan",
5-
"bio": "I am an AWS Professional Services Delivery Consultant specializing in enterprise-scale cloud transformations and modernization initiatives.",
6-
"linkedin": "https://www.linkedin.com/in/shankar-srinivasan-3863a110"
7-
}
8-
],
9-
"cleanup": {
10-
"text": [
11-
"1. Empty the S3 bucket",
12-
"2. Delete the stack: <code>cdk destroy --all</code>"
13-
]
14-
},
15-
"deploy": {
16-
"text": [
17-
"cdk deploy --all"
18-
]
19-
},
20-
"description": "Create an automated workflow using EventBridge Scheduler and Step Functions to synchronize Amazon Bedrock Knowledge Base.",
2+
"title": "Synchronize Amazon Bedrock Knowledge Bases",
3+
"description": "Create an automated workflow using Amazon EventBridge Scheduler and AWS Step Functions to synchronize Amazon Bedrock Knowledge Base.",
214
"framework": "AWS CDK",
225
"gitHub": {
236
"template": {
247
"projectFolder": "eventbridge-scheduled-stepfunction-bedrock-kb-sync",
258
"repoURL": "https://github.com/aws-samples/serverless-patterns/tree/main/eventbridge-scheduled-stepfunction-bedrock-kb-sync",
26-
"templateFile": "kb_sync_stack.py",
9+
"templateFile": "cdk/stacks/kb_infra_stack.py",
2710
"templateURL": "serverless-patterns/eventbridge-scheduled-stepfunction-bedrock-kb-sync"
2811
}
2912
},
3013
"introBox": {
3114
"headline": "How it works",
3215
"text": [
33-
"This sample project demonstrates how to use AWS EventBridge Scheduler to trigger a Step Functions workflow that synchronizes multiple Amazon Bedrock Knowledge Bases. The pattern automates the synchronization process using native service integrations, with a focus on handling multiple Knowledge Bases efficiently.",
34-
"The Step Functions workflow is designed with nested Map states: the outer Map state processes multiple Knowledge Bases, while the inner Map state handles data sources for each Knowledge Base. Although designed for parallel processing, current Bedrock limitations restrict data source synchronization to sequential execution (one at a time) within each Knowledge Base. This architecture ensures scalability when these limitations are lifted in the future.",
35-
"The workflow includes comprehensive status checking and result reporting for each sync operation. For each Knowledge Base, it retrieves all associated data sources, initiates sync operations sequentially, monitors progress, and aggregates results. The pattern deploys one EventBridge Scheduler (running every 15 minutes), one Step Functions state machine with nested Map states, S3 buckets for data sources, and configures the necessary IAM roles and permissions for Bedrock Knowledge Base integration.",
36-
"Note: While the architecture supports parallel processing, current Bedrock service limitations mean data source syncs within each Knowledge Base must run sequentially. The pattern is future-proofed for when these limitations are removed."
16+
"This sample project demonstrates how to use EventBridge Scheduler and a Step Functions workflow to synchronize multiple Amazon Bedrock Knowledge Bases. The pattern automates the synchronization process using native service integrations, with a focus on handling multiple Knowledge Bases efficiently.",
17+
"The Step Functions workflow is designed with nested Map states: the outer Map state processes multiple Knowledge Bases, while the inner Map state handles data sources for each Knowledge Base. Although designed for parallel processing, Amazon Bedrock data source synchronizations are sequential.",
18+
"The workflow includes comprehensive status checking and result reporting for each sync operation. For each Knowledge Base, it retrieves all associated data sources, initiates sync operations sequentially, monitors progress, and aggregates results. The pattern deploys one EventBridge Scheduler schedule (running every 15 minutes), one Step Functions state machine with nested Map states, Amazon S3 buckets for data sources, and configures the necessary IAM roles and permissions for Bedrock Knowledge Base integration."
3719
]
3820
},
3921
"language": "Python",
@@ -56,11 +38,28 @@
5638
},
5739
"testing": {
5840
"text": [
59-
"1. Upload sample documents to the created S3 bucket (kb-data-source-{account-id})",
41+
"1. Upload sample documents to the created Amazon S3 bucket (kb-data-source-{account-id})",
6042
"2. Wait for the next scheduled execution (15-minute intervals)",
6143
"3. Monitor Step Functions execution in AWS Console",
6244
"4. Verify sync status in Bedrock Knowledge Base console"
6345
]
6446
},
65-
"title": "EventBridge Scheduler to Step Functions for Bedrock Knowledge Base Sync"
47+
"cleanup": {
48+
"text": [
49+
"1. Empty the S3 bucket",
50+
"2. Delete the stack: <code>cdk destroy --all</code>"
51+
]
52+
},
53+
"deploy": {
54+
"text": [
55+
"cdk deploy --all"
56+
]
57+
},
58+
"authors": [
59+
{
60+
"name": "Shankar Srinivasan",
61+
"bio": "I am an AWS Professional Services Delivery Consultant specializing in enterprise-scale cloud transformations and modernization initiatives.",
62+
"linkedin": "https://www.linkedin.com/in/shankar-srinivasan-3863a110"
63+
}
64+
]
6665
}

stepfunctions-eventbridge-onpremise-tf/example-pattern.json

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
{
2-
"title": "Step Functions to on-premises API (Terraform)",
3-
"description": "Step Functions performing HTTP call to on-premises API",
4-
"language": "",
5-
"level": "200",
6-
"framework": "Terraform",
7-
"introBox": {
8-
"headline": "How it works",
9-
"text": [
10-
"This sample project demonstrates how to use an AWS Step Functions state machine to call an on-premises API without using an intermediary Lambda function. This pattern is leveraging EventBridge connection to connect to an HTTP endpoint and VPC Lattice to access private resources (in a VPC or on premises).",
11-
"This pattern deploys one Step Functions, one EventBridge connection, a VPC Lattice resource configuration and resource gateway. You need to have a connection between a VPC and a datacenter (using VPN or Direct Connect)."
12-
]
13-
},
2+
"title": "AWS Step Functions to on-premises API (Terraform)",
3+
"description": "AWS Step Functions performing HTTP call to on-premises API",
4+
"language": "",
5+
"level": "200",
6+
"framework": "Terraform",
7+
"introBox": {
8+
"headline": "How it works",
9+
"text": [
10+
"This sample project demonstrates how to use an AWS Step Functions state machine to call an on-premises API without using an intermediary AWS Lambda function. This pattern uses an Amazon EventBridge connection to connect to an HTTP endpoint and VPC Lattice to access private resources (in a VPC or on premises).",
11+
"This pattern deploys one Step Functions, one EventBridge connection, a VPC Lattice resource configuration and resource gateway. You need to have a connection between a VPC and a datacenter (using VPN or Direct Connect)."
12+
]
13+
},
1414
"gitHub": {
1515
"template": {
1616
"repoURL": "https://github.com/aws-samples/serverless-patterns/tree/main/stepfunctions-eventbridge-onpremise-tf",

stepfunctions-eventbridge-onpremise-tf/stepfunctions-eventbridge-onpremise-tf.json

Lines changed: 0 additions & 97 deletions
This file was deleted.

0 commit comments

Comments
 (0)