How aws-samples/amazon-bedrock-workshop works
• Environment Setup & Prerequisites: Represent the “00_Prerequisites” module that ensures the user has the correct environment (notebook environment – either SageMaker Studio, Notebook Instance, or a local setup) and proper AWS IAM permissions for accessing Bedrock.
• Text Generation (01_Text_generation) – focused on generating text and code using Bedrock’s models.
• Knowledge Bases & RAG (02_KnowledgeBases_and_RAG) – demonstrating retrieval augmented generation with external tools (like LangChain).
• Model Customization (03_Model_customization) – showcasing fine-tuning steps on different models.
• Image and Multimodal (04_Image_and_Multimodal) – including submodules such as NovaCanvas and NovaReel, with examples like text-to-image, image inpainting, outpainting, and video generation.
• Agents (05_Agents) – constructing agents that interact with KBs and APIs.
• Open Source Examples (06_OpenSource_examples) – optional examples integrating tools like LangChain and NVIDIA NeMo Guardrails.
• Cross-Region Inference (07_Cross_Region_Inference) – a specialized lab showcasing inference across regions.
• Amazon Bedrock & External Services: Since the workshop is built around Amazon Bedrock, include a central “Amazon Bedrock API” component. Also include connectors/notes for external packages like LangChain, FAISS, and other SDKs mentioned.
• AWS Infrastructure and IAM: Illustrate how the notebooks interact with AWS services. Show that the execution environment (SageMaker or other notebooks) uses AWS IAM roles/credentials to securely call Bedrock APIs.
• Auxiliary Components: Indicate supporting elements where necessary such as the utility scripts (e.g., utility.py and utils.py in various modules), configuration files, and data assets (images, documents, PDFs) that flow into certain lab demos.
Relationships and Interactions
• Link each lab module to the “Amazon Bedrock API” component to show that they leverage API calls to generate text, images, or perform other tasks.
• Integration with external libraries (e.g., LangChain for RAG or text generation) by drawing interfaces or connectors between the lab modules (especially 02 and 06) and these external services.
• Data flow: for instance, user inputs (e.g., emails, text prompts) entering a Text Generation lab, flowing through API calls to Bedrock, and returning generated outputs.
Architectural Patterns and Design Principles
• Integration via API: The central role of Amazon Bedrock as the API provider is the connecting thread across all labs.
• External Dependency and Extendability: Illustrate how open-source tools (LangChain, FAISS, etc.) plug into the architecture for extended functionalities.
Final Steps for the Principal Software Engineer
• Gradually add the central Amazon Bedrock API as the connecting hub.
• External integrations (like LangChain in the RAG and open-source examples labs) are depicted with proper connectors.