BYOC AI: How Indian Banks Can Deploy AI Without Data Leaving Their VPC

Published 2026-05-10

The regulated enterprise dilemma

A bank’s CISO says: “We want AI DevOps agents. But our data cannot leave our AWS account. And we cannot give API keys to a third party.”

This is the BYOC requirement. It’s common in Indian banking, NBFC, insurance, and healthcare. The standard SaaS model doesn’t work because the vendor’s cloud touches customer data.

EAIP’s BYOC architecture

EAIP separates the control plane from the data plane.

Control plane (EAIP-managed):

• Guard Gate — Cedar ACL, rate limiting, injection scan. Receives requests, evaluates policy, proxies to data plane.
• Model Router — LiteLLM routing, cost tracking. Routes to your Bedrock account, not ours.
• Trace Store — WORM audit hash chain. Stores hashes only, not content.
• DPDP Consent Manager — consent records, erasure receipts.

Data plane (your VPC):

• Agent Runtime — runs in your ECS, EC2, or EKS. Makes inference calls to your Bedrock account.
• AWS Bedrock — your account, ap-south-1. EAIP never has credentials.
• RDS / pgvector — your database. EAIP never reads it.
• STS AssumeRole — EAIP assumes a scoped role in your account for observability only. No key sharing.

The key insight: the control plane processes metadata, not data. Policy evaluation in guard-gate operates on request headers and Cedar entities — not on the user’s query content. The user’s query goes directly from the browser to the data plane (agent runtime in your VPC) via an authenticated proxy. The control plane never sees the plaintext query.

Cross-plane authentication

All control-plane to data-plane calls use INTERNAL_SERVICE_TOKEN. This is a shared secret generated at deployment time, stored in your VPC’s Secrets Manager. The control plane cannot make unauthenticated calls to your data plane.

The STS AssumeRole for observability has a policy scoped to:

• cloudwatch:GetMetricData — latency and error rate metrics
• xray:GetTraceSummaries — trace IDs only, not trace content
• No data-plane storage access

What this means for RBI compliance

Under the RBI outsourcing framework, BYOC means EAIP is a “technology service provider” for the control plane only. The data plane runs in your regulated perimeter. Your data doesn’t cross the outsourcing boundary — only telemetry and audit hashes do, and those are non-reversible.