Documentation Index
Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt
Use this file to discover all available pages before exploring further.
Deployment Options
MCP Platform supports multiple deployment methods to fit different infrastructure requirements, from staging to enterprise production environments.EKS + Terraform
Kubernetes on AWSProduction-ready EKS cluster with RDS, Redis, and full infrastructure
ECS + Terraform
Serverless ContainersSimpler AWS deployment with ECS Fargate (no Kubernetes required)
Helm + Kubernetes
Application DeploymentDeploy application on existing Kubernetes clusters with Helm
Choosing Your Deployment Method
EKS + Terraform - Kubernetes on AWS
Best for:- Production Kubernetes workloads
- Organizations wanting AWS-managed Kubernetes
- Teams needing advanced orchestration
- Multi-application shared clusters
- Full Stack: Create new VPC + new EKS cluster + application infrastructure
- Existing VPC: Use existing VPC + create new EKS cluster
- Existing EKS: Use existing cluster + add application infrastructure only
- Managed EKS cluster (Kubernetes 1.33)
- Auto-scaling node groups
- Managed Aurora PostgreSQL with backups
- ElastiCache Redis for performance
- IAM Roles for Service Accounts (IRSA)
- AWS Load Balancer Controller
- CloudWatch observability
- KMS encryption
- AWS account with appropriate permissions
- Terraform 1.7+
- kubectl for cluster access
- Helm 3.8+ for application deployment
ECS + Terraform - Serverless Containers
Best for:- Simpler production deployments
- Organizations wanting serverless containers
- Teams without Kubernetes expertise
- AWS-native deployments
- Minimal: 4 required parameters, smart defaults (fastest deployment)
- Enterprise: 160+ customizable options (full control)
- Auto-scaling ECS Fargate services
- Managed Aurora PostgreSQL with backups
- ElastiCache Redis for performance
- Application Load Balancer with SSL
- CloudWatch monitoring and logging
- VPC with security groups
- Simpler than Kubernetes
- AWS account with appropriate permissions
- Domain name you control (required for SSL auto-creation)
- Terraform 1.5+
- AWS CLI configured
Helm + Kubernetes - Application Deployment
Best for:- Organizations using Kubernetes
- Teams wanting container orchestration
- AWS EKS or other managed Kubernetes services
- Production environments requiring high availability
- Kubernetes-native deployment with Helm charts
- AWS IAM role integration for Bedrock access
- Support for embedded or external databases
- Certificate management (ACM or Let’s Encrypt)
- Horizontal pod autoscaling
- Network policies and security contexts
- Kubernetes 1.19+
- Helm 3.8+
- kubectl configured
- AWS IAM role with Bedrock permissions (for AWS deployments)
Architecture Comparison
EKS + Terraform Architecture
ECS + Terraform Architecture
Component Comparison
| Component | EKS + Terraform | ECS + Terraform | Helm + Kubernetes |
|---|---|---|---|
| Compute | EKS Pods | ECS Fargate | Kubernetes Pods |
| Database | Aurora PostgreSQL | Aurora PostgreSQL | PostgreSQL/External |
| Cache | ElastiCache Redis | ElastiCache Redis | Redis/External |
| Load Balancer | ALB + Ingress | Application LB | Ingress Controller |
| Monitoring | CloudWatch | CloudWatch | Basic health checks |
| Scaling | HPA + Cluster Autoscaler | Auto-scaling | HPA |
| Backups | Automated | Automated | Manual |
| Complexity | High | Medium | Medium |
| Cost | $200-800/mo | $130-225/mo | Varies |
Security Considerations
EKS + Terraform Security
- VPC with private subnets
- Security groups with least privilege
- KMS encryption for Kubernetes secrets
- IAM Roles for Service Accounts (IRSA)
- Network policies for pod isolation
- Pod security contexts
- Encrypted databases and storage
- SSL/TLS with ACM certificates
- CloudTrail for audit logging
ECS + Terraform Security
- VPC with private subnets
- Security groups with least privilege
- Encrypted databases and storage
- SSL/TLS termination at load balancer
- Secrets management with AWS Secrets Manager
- CloudTrail for audit logging
- Task role IAM policies
Kubernetes Security (Helm)
- Network policies for pod isolation
- Pod security contexts
- Service account with IAM role integration
- Encrypted secrets with Kubernetes secrets
- RBAC for fine-grained access control
Cost Considerations
EKS + Terraform
Estimated Monthly Cost (us-east-1):- Full Stack: $723-1,088/month
- EKS control plane: $73
- EC2 nodes (4x m6i.2xlarge): $400-500
- Aurora PostgreSQL (2-16 ACUs): $60-240
- ElastiCache Redis: $40-50
- NAT Gateways (3 AZs): $100-120
- ALB + Data Transfer: $40-80
- Existing VPC: Save $100-120/month (no NAT Gateway costs)
- Existing EKS: $150-395/month (RDS + Redis + data transfer only)
ECS + Terraform
Estimated Monthly Cost (us-west-2):- Minimal Configuration: $130-225/month
- Aurora PostgreSQL (2-16 ACUs)
- ECS Fargate (2 backend + 2 frontend)
- ElastiCache Redis
- Application Load Balancer
- Enterprise Configuration: $360-950/month
- Higher capacity database and compute
- Enhanced monitoring and backups
- Custom scaling and security
Helm + Kubernetes
Cost: Depends on your Kubernetes infrastructure- AWS EKS: Use EKS + Terraform above
- Self-managed: Your infrastructure costs
- Other cloud providers: Varies by provider and configuration
Performance Characteristics
| Deployment | Response Time | Throughput | Availability |
|---|---|---|---|
| EKS + Terraform | < 100ms | 1000+ req/s | 99.9%+ |
| ECS + Terraform | < 100ms | 1000+ req/s | 99.9%+ |
| Helm + Kubernetes | < 150ms | 500+ req/s | 99.5%+ |
Getting Started
Next Steps
EKS + Terraform
Deploy Kubernetes infrastructure on AWS EKS
ECS + Terraform
Deploy serverless containers on AWS ECS
Helm + Kubernetes
Deploy application on Kubernetes with Helm