Getting Started with Infrastructure

This guide walks you through deploying your first piece of infrastructure with Infrastructure. By the end, you will have connected a cloud provider, created a Cloud Resource, and watched a Stack Job provision it.

Prerequisites

• A Planton account with an organization
• An environment created in your organization (see Platform Getting Started)
• Access to a cloud provider account (AWS, GCP, or Azure) or a Kubernetes cluster

Step 1: Connect a Cloud Provider

Before Infrastructure can provision infrastructure, it needs credentials for your cloud provider. Navigate to Connect in the web console and add your provider credentials.

Each provider has its own connection type — AWS connections use access keys or cross-account roles, GCP connections use service account keys, Azure connections use service principals, and Kubernetes connections use kubeconfig files.

See the Connections section for detailed setup instructions for each provider.

Step 2: Map Credentials to Your Environment

After adding a connection, authorize it for the environment where you want to deploy. This tells Planton which credentials to use when provisioning resources in that environment.

If this is your first connection for a provider, you can also set it as the default — so you do not need to specify the connection explicitly every time you create a resource.

See Environment Mappings and Default Connections for details.

Step 3: Browse the Catalog

Navigate to the Deployment Component Store in the web console to see what you can deploy. The catalog shows all available resource types — AWS VPCs, GCP Cloud SQL instances, Kubernetes deployments, and more — organized by provider.

Select a resource type to start configuring it for deployment.

See Cloud Resource Kinds for an overview of the full catalog.

Step 4: Create a Cloud Resource

Select a resource type from the catalog, configure it for your target environment, and deploy. The web console guides you through the configuration — selecting the environment, setting resource-specific options, and reviewing before submission.

You can also create a Cloud Resource from the CLI using a YAML manifest:

planton create -f my-resource.yaml

See Cloud Resources for the full lifecycle and configuration options.

Step 5: Monitor the Stack Job

When you submit the Cloud Resource, a Stack Job is created automatically. The job initializes the IaC module, refreshes state, previews changes, and applies them. Watch progress in real time from the web console or CLI:

planton stack-job stream-progress-events <stack-job-id>

The Stack Job detail page shows each operation step with its status — initialize, refresh, preview, apply — along with resource-level logs showing exactly what is being created.

What to Explore Next

• Infra Charts — Bundle multiple resources into reusable templates
• Infra Projects — Deploy coordinated multi-resource environments
• Infra Pipelines — Orchestrate deployments with dependency ordering
• Flow Control — Add governance policies for production deployments