Management
Ongoing management of your CorpAI deployment.
Health Monitoring
Check Data Plane health in Settings:
| Status | Meaning |
|---|---|
| Healthy | All systems operational |
| Propagating | DNS propagating (wait up to 30 min) |
| Unhealthy | Check NAT Gateway, security groups |
Credentials
See Getting Started for adding credentials. Credentials are stored in your AWS Secrets Manager and accessed by MCP servers via IRSA.
For services running in your VPC, use the endpoint DNS from VPC Connections as the host.
MCP Servers
See Getting Started for deploying servers.
| Status | Meaning |
|---|---|
| Running | Operational |
| Deploying | In progress |
| Failed | Check logs (see below) |
Viewing Logs
Via kubectl
Configure kubectl access:
aws eks update-kubeconfig --name corpai-cluster --region {region}View Data Plane API logs:
kubectl logs -l app=data-plane-api -n {namespace} -fList MCP server pods:
kubectl get pods -n {namespace}View MCP server logs:
kubectl logs -l app=mcp-github -n {namespace} -fVia AWS Console
View logs in CloudWatch:
- Go to CloudWatch → Log groups
- Find
/aws/eks/corpai-cluster/clusterfor cluster logs - Find
/corpai/*/data-planefor application logs
EKS Console Access
To view pods in the AWS Console, you need to add your IAM user/role to the EKS cluster’s aws-auth ConfigMap.
Get current ConfigMap:
kubectl get configmap aws-auth -n kube-system -o yaml > aws-auth.yamlAdd your IAM user/role:
mapUsers: |
- userarn: arn:aws:iam::{account-id}:user/{username}
username: {username}
groups:
- system:mastersApply the change:
kubectl apply -f aws-auth.yamlBackups
| Component | Backup | Retention |
|---|---|---|
| RDS | Automated snapshots | 7 days |
| S3 | Versioning enabled | 90 days |
Restore via AWS Console if needed.
Support
- Email: support@corpai.io
- Include: Organization ID, error messages, timestamps
Next
Security →
Last updated on