Infrastructure Blueprints

Blueprints are pre-built Terraform templates for common infrastructure patterns. The Blueprint Wizard guides you through provider selection and parameter configuration, then generates a complete, ready-to-deploy IaC project — no code required.

Available Blueprints

Cloud Provider Support

Using the Blueprint Wizard

Blueprint Parameters

Kubernetes Cluster

What gets created (AWS EKS example):

• VPC with public and private subnets across two availability zones
• Internet Gateway and NAT Gateway
• EKS cluster with OIDC provider enabled
• Managed node group with the configured instance type and count
• IAM role for the cluster (eks.amazonaws.com trust policy)
• IAM role for nodes with AmazonEKSWorkerNodePolicy and AmazonEC2ContainerRegistryReadOnly
• Security groups with appropriate inbound/outbound rules

Database

Static Website

Data Processing (EMR / Dataproc / HDInsight)

Generated Project Structure

Every blueprint produces a complete, organized Terraform project:

project-name/
├── main.tf          # Primary resource definitions
├── variables.tf     # Input variables with types and defaults
├── outputs.tf       # Output values (endpoints, IDs, ARNs)
├── providers.tf     # Provider configuration and version constraints
└── iam.tf           # IAM roles and policies (where applicable)

For Kubernetes and networking-heavy blueprints, networking resources are split into a separate file:

project-name/
├── main.tf
├── vpc.tf           # VPC, subnets, gateways, route tables
├── iam.tf
├── variables.tf
└── outputs.tf

Example: Kubernetes Cluster Blueprint (AWS)

Input Parameters

Produced main.tf (excerpt)

resource "aws_eks_cluster" "main" {
  name     = var.cluster_name
  role_arn = aws_iam_role.cluster.arn
  version  = var.kubernetes_version

  vpc_config {
    subnet_ids              = concat(aws_subnet.private[*].id, aws_subnet.public[*].id)
    endpoint_private_access = true
    endpoint_public_access  = true
  }

  depends_on = [
    aws_iam_role_policy_attachment.cluster_policy,
    aws_iam_role_policy_attachment.vpc_resource_controller,
  ]

  tags = {
    Name      = var.cluster_name
    ManagedBy = "ops0"
  }
}

resource "aws_eks_node_group" "main" {
  cluster_name    = aws_eks_cluster.main.name
  node_group_name = "${var.cluster_name}-nodes"
  node_role_arn   = aws_iam_role.node.arn
  subnet_ids      = aws_subnet.private[*].id

  scaling_config {
    desired_size = var.node_count
    max_size     = var.node_count * 2
    min_size     = 1
  }

  instance_types = [var.node_size]

  depends_on = [
    aws_iam_role_policy_attachment.node_policy,
    aws_iam_role_policy_attachment.cni_policy,
    aws_iam_role_policy_attachment.ecr_read,
  ]
}

Cost Estimate Before Deploying

After the project is created, run a cost estimate in the deployment flow:

Customizing Blueprints

Blueprints are starting points, not locked templates. Once ops0 creates the IaC project from a blueprint, it behaves like any other IaC project — you can:

• Edit files directly in the editor
• Ask the AI to modify the generated code ("add a second node group for spot instances")
• Add additional resources (monitoring, logging, alerting)
• Change variable defaults in variables.tf
• Refactor into modules

From Blueprint to Deployed Infrastructure

Related