GCP Cloud Composer Env Builder

ServerlessGCP

Build Cloud Composer environment configurations with Airflow settings, workload sizing, and private networking.

Cloud Composer Configuration

Build Cloud Composer environment configurations with Airflow settings, workload sizing, private networking, and CMEK encryption.

Required Fields

nameconfig.softwareConfig.imageVersionconfig.nodeConfig.networkconfig.environmentSize

{
  "name": "projects/my-project/locations/us-central1/environments/prod-composer",
  "config": {
    "softwareConfig": {
      "imageVersion": "composer-3-airflow-2.9.3",
      "pypiPackages": {
        "apache-airflow-providers-google": ">=10.0.0",
        "pandas": ">=2.0.0",
        "sqlalchemy": ">=2.0.0"
      },
      "envVariables": {
        "ENVIRONMENT": "production",
        "DAG_TIMEOUT_MINUTES": "120"
      },
      "airflowConfigOverrides": {
        "core-max_active_runs_per_dag": "3",
        "core-parallelism": "64",
        "scheduler-dag_dir_list_interval": "60",
        "webserver-dag_default_view": "graph"
      }
    },
    "workloadsConfig": {
      "scheduler": {
        "cpu": 2,
        "memoryGb": 7.5,
        "storageGb": 5,
        "count": 2
      },
      "webServer": {
        "cpu": 2,
        "memoryGb": 7.5,
        "storageGb": 5
      },
      "worker": {
        "cpu": 2,
        "memoryGb": 7.5,
        "storageGb": 5,
        "minCount": 2,
        "maxCount": 10
      },
      "triggerer": {
        "cpu": 1,
        "memoryGb": 1,
        "count": 1
      }
    },
    "nodeConfig": {
      "network": "projects/my-project/global/networks/prod-vpc",
      "subnetwork": "projects/my-project/regions/us-central1/subnetworks/composer-subnet",
      "serviceAccount": "composer-sa@my-project.iam.gserviceaccount.com",
      "tags": ["composer-node"],
      "enableIpMasqAgent": true,
      "ipAllocationPolicy": {
        "clusterSecondaryRangeName": "composer-pods",
        "servicesSecondaryRangeName": "composer-services"
      }
    },
    "privateEnvironmentConfig": {
      "enablePrivateEnvironment": true,
      "enablePrivatelyUsedPublicIps": false,
      "cloudSqlIpv4CidrBlock": "10.50.0.0/12",
      "webServerIpv4CidrBlock": "10.60.0.0/24"
    },
    "encryptionConfig": {
      "kmsKeyName": "projects/my-project/locations/us-central1/keyRings/composer-ring/cryptoKeys/composer-key"
    },
    "environmentSize": "ENVIRONMENT_SIZE_MEDIUM"
  },
  "labels": {
    "team": "data-engineering",
    "environment": "production"
  }
}

Generated Output

Output will appear here...

How It Helps

Build Cloud Composer environment configurations with Airflow settings, workload sizing, and private networking. This tool helps GCP engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

Things Engineers Ask

Can I use this Cloud Composer Env builder for Google Cloud sovereign or assured workloads?

Most Cloud Composer Env primitives behave the same in standard, Assured Workloads, and sovereign Google Cloud deployments, but available services, regions, and access controls differ. The output is portable in shape; you must verify service availability and any Assured Workloads constraints before applying in a controlled environment.

Will the output of this Cloud Composer Env builder pass `gcloud ... --validate-only` or `terraform validate`?

It produces structurally valid output for the GCP schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the message points at the exact attribute the schema rejected.

Practical Applications

1Designing a Cloud Composer Env configuration for a new GCP workload where the team wants the spec reviewed before any console click happens.
2Pre-flighting a Cloud Composer Env change against a change-management ticket so the implementation matches what was approved.
3Building a Cloud Composer Env reference implementation for a partner integration where you cannot rely on console access.
4Onboarding a new engineer by giving them a Cloud Composer Env sandbox to iterate on without touching live projects.

Related Learning Guides

Cloud Functions vs Cloud Run24 min read
Pub/Sub & Event-Driven Architecture25 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.