Skip to Content
ArchitectureData Plane

Data Plane

The Data Plane runs in your AWS account. Handles MCP server execution, AI processing, policies, and data storage.

Infrastructure

ResourcePurpose
EKSMCP servers, Data Plane API
RDS PostgreSQLConversations, config, audit
ElastiCache ValkeyCaching, rate limiting
S3Document storage
Bedrock + OpenSearchAI (Gemma 3 12B) and vector search
Secrets ManagerMCP credentials

Data Residency

DataLocationEncryption
DocumentsS3KMS
ConversationsRDSKMS
MCP credentialsSecrets ManagerKMS
EmbeddingsOpenSearchKMS

Data Plane API

Runs in your EKS cluster. Your endpoint URL is displayed in Settings → Infrastructure after deployment.

Handles:

  • JWT-authenticated requests from Control Plane
  • AI processing via Bedrock (Gemma 3 12B)
  • MCP server management
  • Document uploads and Knowledge Base queries

MCP Server Execution

Each MCP server runs as a Kubernetes deployment:

  • Isolated namespace
  • IRSA for AWS credentials (no static keys)
  • Secrets from your Secrets Manager
  • Network policies for egress control

Supported Regions

All major AWS regions including:

AmericasEuropeAsia Pacific
us-east-1 (Virginia)eu-west-1 (Ireland)ap-southeast-1 (Singapore)
us-east-2 (Ohio)eu-west-2 (London)ap-southeast-2 (Sydney)
us-west-1 (California)eu-west-3 (Paris)ap-northeast-1 (Tokyo)
us-west-2 (Oregon)eu-central-1 (Frankfurt)ap-northeast-2 (Seoul)
ca-central-1 (Canada)eu-north-1 (Stockholm)ap-south-1 (Mumbai)
sa-east-1 (São Paulo)

Outbound Connectivity

DestinationPathPurpose
*.corpai.ioNAT GatewayControl Plane
S3, ECR, STS, BedrockVPC EndpointsAWS services (private, no internet)
External APIsNAT GatewayMCP integrations (GitHub, Jira, etc.)

Next

Request Flow

Last updated on