Cloud Setup
Service configuration reference
Every supported simulation and deployment service with the configuration fields CloudWatcher uses.
Use this page when you want the exact service-level configuration map. It is useful for developers building a simulation, reviewing Terraform output, debugging deployment validation, or comparing AWS, Azure, and GCP service support.
All service configuration fields
- GitHub Repository: used for application bootstrap. Configure Git URL, branch, optional token, project type, runtime, build command, start command, app port, frontend directory, backend directory, API path, and backend port. CloudWatcher uses it to pull code and prepare a deployment plan.
- Docker Hub: used for container-based bootstrap. Configure repository, tag, username, password, app port, and container port. CloudWatcher uses it to pull or reference an image for a cloud deployment flow.
- AWS EC2 Instance: used for virtual machines. Configure instance type, count, region, AMI, key name, instance name, admin username, VPC ID, subnet ID, and security group. CloudWatcher turns this into compute infrastructure and can estimate, deploy, inspect, and clean it up in simulations.
- AWS S3 Bucket: used for object storage. Configure bucket name, region, versioning, public access, lifecycle rule, and policy. CloudWatcher uses it for storage architecture, cost estimation, Terraform generation, and live inventory where connected.
- AWS RDS Database: used for managed relational databases. Configure engine, engine version, instance class, Multi-AZ, storage GB, storage type, database name, username, port, and public access. CloudWatcher uses these fields to build database Terraform and evaluate database cost/risk.
- AWS Lambda Function: used for serverless compute. Configure runtime, handler, memory MB, timeout seconds, function name, environment, and code. CloudWatcher uses it for serverless simulations, live inspection, and Lambda code viewing where supported.
- AWS DynamoDB Table: used for NoSQL data. Configure table name, billing mode, hash key, hash key type, and region. CloudWatcher uses it for architecture planning and billing-aware simulation.
- AWS API Gateway: used for managed APIs. Configure name, protocol type, endpoint type, and region. CloudWatcher uses it to model API entry points and connect serverless or backend workloads.
- AWS ECS Cluster: used for container services. Configure cluster name, service name, launch type, Fargate Spot, Service Connect, autoscaling, capacity limits, CPU target, sidecar, desired count, CPU, memory, app port, and region.
- AWS EKS Cluster: used for managed Kubernetes. Configure cluster name, Kubernetes version, node count, instance type, app port, and region. CloudWatcher uses it for Kubernetes architecture simulation and cost-aware planning.
- AWS ECR Registry: used for Docker image storage. Configure repository settings and image workflow details. CloudWatcher uses it with container deployments and image verification paths.
- AWS Elastic IP: used for static public IPv4 addresses. Configure address attachment intent and region. CloudWatcher models public connectivity and deployment outputs around it.
- AWS Security Group: used as a virtual firewall. Configure inbound rules, SSH, HTTP, HTTPS, private mode, and region. CloudWatcher uses it to model network exposure and deployment security.
- AWS Target Group: used for load-balancer routing. Configure target group name, port, protocol, health path, and target settings where supported. CloudWatcher connects compute nodes to load balancers through it.
- AWS EBS Volume: used for block storage. Configure volume name, size, type, region, and attachment intent. CloudWatcher models persistent disk cost and VM attachment relationships.
- AWS VPC: used for private networking. Configure VPC name, CIDR block, subnet CIDR block, SSH port, HTTP port, HTTPS port, private mode, and region. CloudWatcher uses it as the network base for compute, load balancing, and database nodes.
- AWS Elastic Load Balancer: used for traffic distribution. Configure load balancer name, port, protocol, and region. CloudWatcher uses it to model public traffic entry and backend routing.
- AWS Auto Scaling Group: used for elastic compute capacity. Configure min size, max size, desired capacity, instance type, region, AMI, key name, instance name, admin username, and CPU target.
- AWS CloudFront Distribution: used for CDN delivery. Configure distribution name, origin, cache behavior, and region/global delivery fields where supported. CloudWatcher uses it to model global edge delivery.
- Azure Virtual Machine: used for Azure compute. Configure VM size, count, admin username, instance name, OS disk type, image publisher, image offer, image SKU, and region.
- Azure Storage Account: used for Blob/object storage. Configure storage account name, account tier, replication type, account kind, region, and policy.
- Azure SQL Database: used for managed SQL. Configure database name, SKU name, max size bytes, collation, and region.
- Azure Function App: used for serverless compute. Configure function name, SKU name or consumption plan, and region.
- Azure Virtual Network: used for private networking. Configure VNet name, address space, subnet CIDR block, SSH port, HTTP port, HTTPS port, private mode, and region.
- Azure Container Registry: used for Docker images. Configure registry name, SKU, region, and image workflow settings where supported.
- Azure Public IP: used for public addressing. Configure public IP name, allocation mode, SKU, region, and attachment intent where supported.
- Azure Network Security Group: used for firewall rules. Configure security rules, ports, private mode, and region. CloudWatcher uses it to model access boundaries around Azure workloads.
- Azure Backend Address Pool: used for load-balancer backend routing. Configure backend pool name, port/routing relationships, and region where supported.
- Azure Managed Disk: used for VM disk storage. Configure disk name, size, type, region, and attachment intent.
- Azure AKS Cluster: used for managed Kubernetes. Configure cluster name, node count, node VM size, DNS prefix, and region.
- Azure Load Balancer: used for traffic distribution. Configure load balancer name, frontend port, backend port, and region.
- Azure VM Scale Set: used for autoscaling VM groups. Configure min size, max size, desired capacity, VM size, region, and autoscaling settings where supported.
- Azure CDN or Front Door: used for global delivery and edge routing. Configure CDN name, origin, SKU, and routing behavior where supported.
- GCP Compute Engine VM: used for Google Cloud compute. Configure instance name, machine type, zone, image, boot disk GB, allow HTTP, and region.
- GCP Cloud Storage Bucket: used for object storage. Configure bucket name, storage class, location, versioning, region, and policy.
- GCP Cloud SQL Database: used for managed relational data. Configure instance name, database name, database version, tier, and region.
- GCP Cloud Run Function: used for serverless functions. Configure function name, runtime, entry point, and region.
- GCP VPC Network: used for private networking. Configure network name, CIDR block, subnet CIDR block, SSH port, HTTP port, HTTPS port, private mode, and region.
- GCP GKE Cluster: used for managed Kubernetes. Configure cluster name, node count, machine type, location, and region.
- GCP Artifact Registry: used for container images. Configure repository, format, region, and image workflow settings where supported.
- GCP External Address: used for static public IP addressing. Configure address name, region, and attachment intent where supported.
- GCP Firewall Rule: used for traffic control. Configure allowed ports, source ranges, target tags, private mode, and region/network settings.
- GCP Backend Service: used for load-balancer backends. Configure backend name, protocol, port, health check, and balancing settings where supported.
- GCP Persistent Disk: used for block storage. Configure disk name, size, type, zone, and attachment intent.
- GCP Cloud Load Balancer: used for traffic distribution. Configure load balancer name, port, protocol, backend service, and region/global routing.
- GCP Managed Instance Group: used for scalable compute. Configure group name, machine type, min size, max size, desired capacity, region or zone, and autoscaling policy.
- GCP Cloud CDN: used for edge caching. Configure CDN name, backend bucket or service, cache behavior, and global delivery settings where supported.
How to read these configs
- Required identity and billing setup still happens in AWS, Azure, GCP, GitHub, AI keys, or reports settings before a workflow can use these services.
- Simulation fields describe planned infrastructure. They become real only when a deployment is started with valid credentials.
- Live Infrastructure fields come from discovered provider resources and may not include every field used during simulation.
- Cost estimates depend on pricing data, selected region, resource size, runtime, and provider availability.
- Provider errors such as quota, SKU unavailable, permission denied, invalid region, missing API, or naming conflict must be fixed in the provider account before retrying.
Need more help?
Keep moving with the right next guide
If your team still runs into setup issues, empty dashboards, billing delays, callback failures, or alerting problems, continue with troubleshooting before re-running the entire onboarding flow.