Instance Management
An Infrastream instance is the set of resources that Infrastream installs and runs for your organization. This page covers how Infrastream sets up an instance, how it links to the control plane and how it upgrades.
Where things run
- Infrastream Cloud: your apps and data run in Google Cloud projects that Infrastream operates and bills.
- Private Cloud: your apps and data run in your own Google Cloud organization, billed to your own billing account.
- Both plans: the control plane, the assistant (Beck) and the state database run in Infrastream's organization.
An instance includes:
- a Google Cloud project with the required APIs;
- the Cloud Run services: the portal, the runner and the webhook processors;
- a Spanner instance;
- the assistant, which runs on Vertex AI Agent Engine;
- the network and the service accounts.
Onboarding
On Private Cloud you need a region and a Google Cloud organization with an active billing account. You also need an Organization Admin who can grant the IAM permissions. On Infrastream Cloud you need none of these.
The portal installs an instance in two phases:
- Discovery. It scans the Google Cloud organization that it installs into, to find components that exist. This lets an interrupted install resume. It also finds version mismatches and checks health.
- Install. Each step finds its component or creates it. A step skips a component that exists and is healthy.
| Group | Components |
|---|---|
| Foundation | Folder, security tags, organization policies |
| Project | Project, billing link, API enablement |
| Identity | Service accounts and IAM bindings |
| Network | VPC, subnets, firewall rules, Private Service Connect endpoint |
| Security | Artifact Registry, Binary Authorization policy |
| Assistant | Service account, permissions, bucket, configuration secret, agent runtime |
| Data | Spanner instance |
| Runtime | Cloud Run services, load balancer, IAP |
The installation status is one of Installed, Out of Date (a newer version exists), Partial (some components are not ready) or Error (a component failed).
Link to the control plane
Each instance connects to the control plane over Private Service Connect. This is a private link, not the public internet. It has two uses:
- License and features. At the start of each engine run, the instance checks the license and reads the feature flags. If the control plane is not reachable, the engine continues. It keeps the infrastructure that exists and does not change resources that depend on an add-on until the link returns. The engine never blocks on this check.
- Error reports. When a resource fails, the engine sends a structured error report to the control plane. Infrastream engineers use these reports to find problems early.
The state database, the control plane and the assistant run in Infrastream's organization on both plans. So Infrastream holds the recorded state of your resources. Beyond that, your instance sends only the error reports and what the assistant needs to answer you.
Upgrades
The portal marks an instance Out of Date when a new version exists. You start the upgrade in the portal. It sets the target version, resolves the image digests, redeploys the Cloud Run services and the assistant, and checks the status again. Only components that need an update change.