Self Hosted CloudAEye

Deploy CloudAEye Code Review in your own AWS account with the CloudAEye Terraform configuration. Supports customer controlled infrastructure, VPC data storage, private networking, and configurable LLM providers.

Overview

CloudAEye self hosted Code Review runs inside the customer's AWS account. Customer administrators control the AWS account, Terraform state, network access, IAM access, backups, logs, and operational monitoring.

The default stack creates:

• VPC networking with public and private subnets.
• A public Application Load Balancer for the CloudAEye UI, APIs, SSO routes, and GitHub webhooks.
• ECS Managed Instances for application services, workers, MongoDB, and ChromaDB.
• Private MongoDB and ChromaDB ECS services with ECS-managed EBS volumes.
• SQS queues for indexing and asynchronous code review work.
• Amazon Cognito resources for user authentication and tenant bootstrap.
• CloudWatch log groups and ECS Container Insights.

MongoDB, ChromaDB, and background workers are not exposed through the public load balancer.

Deployment

• CloudAEye currently supports AWS ECS for self hosted Code Review.
• The Terraform bundle provisions the AWS infrastructure and deploys CloudAEye containers from the CloudAEye on-prem ECR release repository.
• The Application Load Balancer is the only public ingress path.
• Restrict inbound access with allowed_app_cidr before production use.
• Private ECS tasks use the NAT gateway for outbound access to ECR, AWS APIs, source control providers, license validation, and configured LLM providers.
• Customer-specific configuration is supplied through terraform.tfvars.

Default deployment resources:

Layer	Default AWS resources
Entry point	Application Load Balancer
Runtime	ECS cluster with ECS Managed Instances
Private services	MongoDB, ChromaDB, cloudaeye-indexer-worker
Queues	cloudaeye-indexing-queue, cloudaeye-review-queue
Authentication	Amazon Cognito
Logs and metrics	CloudWatch log groups and ECS Container Insights

LLM Configuration

• Customers can provide there own LLM credentials.
• Set llm_model to a model supported by the selected provider.
• Terraform saves the selected LLM preference to the DB.

Database

• MongoDB stores CloudAEye application data, tenant state, repository integration state, review results, and related runtime data.
• ChromaDB stores vectorized code context used during review generation.
• MongoDB and ChromaDB are reachable only from private ECS tasks through security groups and Cloud Map private DNS.

Default data services:

Service	Storage	Exposure
MongoDB	ECS-managed encrypted EBS volume	Private ECS service
ChromaDB	ECS-managed encrypted EBS volume	Private ECS service

Version Management

• CloudAEye publishes release images once a month. We might releases multiple patches to resolve customer issues.
• Set onprem_release_tag before deployment to choose the released image set.
• We will send you an email when a new version is available.

Code Host Support

• The default self hosted Terraform configuration is configured for GitHub App based code review.
• GitHub App setup requires the GitHub App ID, installation ID, private key, webhook secret, and either a GitHub organization or user.
• The public webhook route is /github-app/webhook.

Pricing Structure

• Self-hosted CloudAEye Code Review is available through CloudAEye commercial agreements.
• Contact CloudAEye for pricing, release image access, licensing terms, and production support options.
• Customer teams remain responsible for AWS infrastructure costs, including ECS, EC2 capacity, EBS volumes, SQS, Cognito, CloudWatch, load balancing, NAT gateway, data transfer, backups, and any selected LLM provider usage if you use your own key.

Getting Started

To deploy CloudAEye self-hosted Code Review:

1. Review the System Architecture.
2. Follow the Self-Hosted Deployment Guide.
3. Configure SSO if required using Okta or Keycloak.
4. Contact CloudAEye support for release image access, deployment questions, pricing, and production readiness review.