Skip to content

AIP-C01 · Study Guide

← Domain 2: Implementation and Integration

2.1.7 · Lesson 7 of 25

Model Extension Frameworks

MCP servers can expose tools to AI systems.

Overview

MCP servers can expose tools to AI systems.

Two important implementation patterns from the outline:

Lambda MCP Server

Use Lambda for lightweight/stateless MCP functionality.

Agent
 ↓
MCP Client
 ↓
MCP Server
 ↓
Lambda
 ↓
Tool

Good conceptual fit:

  • lightweight tools
  • stateless operations
  • event-driven/serverless execution

ECS MCP Server

Use Amazon ECS when the MCP server needs more complex containerized execution.

Agent
 ↓
MCP Client
 ↓
MCP Server
 ↓
ECS
 ↓
Complex Tool

This is useful when the tool environment needs more control or complexity than a simple Lambda function.

MCP Client Libraries

Client libraries provide a consistent access pattern.

Agent Application
       ↓
MCP Client Library
       ↓
MCP Server
       ↓
Tools

High-yield comparison

TechnologyMain purpose
Strands AgentsBuild agentic applications
Agent SquadMulti-agent coordination
MCPStandardized agent/tool interaction
Step FunctionsWorkflow orchestration/state
LambdaServerless execution
ECSContainerized/complex tool execution
IAMPermission boundaries

2.2 — Implement Model Deployment Strategies

This section is about where and how the foundation model runs or is accessed.

The deployment choice depends on:

Performance
+ Cost
+ Latency
+ Traffic
+ Model size
+ GPU requirements
+ Availability
+ Scaling requirements

Key points

  • lightweight tools
  • stateless operations
  • event-driven/serverless execution
  • Lambda MCP Server
  • ECS MCP Server
  • MCP Client Libraries

Exam focus

2.2 — Implement Model Deployment Strategies This section is about where and how the foundation model runs or is accessed. The deployment choice depends on: Performance

View progress