Skip to content

Commit 81be538

Browse files
committed
Merge branch 'fix/update-agentic-readmes-with-arch-diagrams' into 'develop'
Adding architecture diagrams to relevant READMEs See merge request genaiic-reusable-assets/engagement-artifacts/genaiic-idp-accelerator!286
2 parents b4a7f5f + 591a28a commit 81be538

File tree

4 files changed

+8
-19
lines changed

4 files changed

+8
-19
lines changed

docs/agent-analysis.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,15 +37,18 @@ https://github.com/user-attachments/assets/e2dea2c5-5eb1-42f6-9af5-469afd2135a7
3737

3838
## Architecture
3939

40+
The architecture of the Agent Analysis feature is shown below. The Web UI and AppSync API components are the same as used by the rest of the IDP system (with new AppSync endpoints added). Note the inclusion of Amazon Athena and the AgentCore Code Interpreter is specific to the Analytics Agent, but the Agent Request Handler and Processor lambdas along with jobs table are used for all agents, including [MCP agents](./custom-MCP-agent.md).
41+
42+
![Architecture Diagram](../images/IDP-AnalyticsAgent.drawio.png)
43+
4044
### Multi-Agent System
4145

4246
The Agent Analysis feature uses a multi-agent architecture with:
4347

4448
1. **Orchestrator Agent**: Routes queries to appropriate specialized agents based on query content and agent capabilities
4549
2. **Analytics Agent**: Handles data analysis, SQL generation, and visualization creation
46-
3. **Dummy Agent**: Provides simple calculations and development testing capabilities
47-
4. **External MCP Agents**: Custom agents connected via Model Context Protocol servers
48-
5. **Extensible Framework**: Easy addition of new specialized agents for specific use cases
50+
3. **External MCP Agents**: Custom agents connected via Model Context Protocol servers
51+
4952

5053
### Agent Workflow
5154

docs/custom-MCP-agent.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -20,23 +20,9 @@ The External MCP Agent allows you to:
2020
- **Real-time Integration**: Tools are available immediately through the IDP web interface
2121

2222
## Architecture
23+
An example architecture demonstrating the authentication flow and connections between the MCP Client (running in the IDP application) and an external MCP Server (deployed outside of the IDP application) can be seen below. The `get_client_address` and `send_verification_email` APIs drawn are just for demonstration purposes.
2324

24-
```
25-
┌─────────────────────┐ ┌──────────────────────┐ ┌─────────────────────┐
26-
│ IDP Solution │ │ Your AWS Account │ │ Your MCP Server │
27-
│ │ │ │ │ │
28-
│ ┌─────────────────┐ │ │ ┌──────────────────┐ │ │ ┌─────────────────┐ │
29-
│ │ External MCP │ │ │ │ AWS Cognito │ │ │ │ Custom Tools │ │
30-
│ │ Agent │◄┼────┼─┤ User Pool │◄┼────┼─┤ - Calculator │ │
31-
│ │ │ │ │ │ │ │ │ │ - Weather API │ │
32-
│ └─────────────────┘ │ │ └──────────────────┘ │ │ │ - Database │ │
33-
│ │ │ │ │ │ - Custom Logic │ │
34-
│ ┌─────────────────┐ │ │ │ │ └─────────────────┘ │
35-
│ │ AWS Secrets │ │ │ │ │ │
36-
│ │ Manager │ │ │ │ │ │
37-
│ └─────────────────┘ │ │ │ │ │
38-
└─────────────────────┘ └──────────────────────┘ └─────────────────────┘
39-
```
25+
![Architecture Diagram](../images/IDP-external-mcp-example.drawio.png)
4026

4127
## Prerequisites
4228

82.1 KB
Loading
61.4 KB
Loading

0 commit comments

Comments
 (0)