One manifest, two clouds: multi-cloud infrastructure with stackql-deploy
Tutorial 3 introduced stackql-deploy against a single Google Cloud project. One manifest, one provider, one VPC. The framework proved its shape: declarative resources described as SQL-anchored files, an exists-create-statecheck-exports loop that runs idempotently against live cloud APIs, no state file to maintain. This tutorial takes the same framework and puts it to work across two clouds at…
This tutorial expands the previous stackql-deploy example to work across two different cloud providers simultaneously. A single manifest declares infrastructure for both Google Cloud Platform (GCP) and Amazon Web Services (AWS), provisioning both VPCs in one build command. The manifest serves as the sole source of truth for the multi-cloud infrastructure, integrating features like per-environment values, tag-based resource identification, resource composability, and provider-specific query helpers.
The AWS section of the walkthrough demonstrates additional capabilities not required in the simpler GCP example, including per-environment CIDR blocks, AWS-specific variable names, and provider-specific helpers that keep the manifest declarative despite wire-format differences.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
