Skip to main content

Deploy

Amnify’s Deploy feature lets you provision and manage cloud infrastructure through a guided UI. Under the hood it uses Terraform, but you interact with it through templates, a step-by-step wizard, and visual plan/approve/apply workflows — no CLI required.

Core concepts

Templates

Reusable Terraform blueprints for cloud resources (VPCs, EC2 instances, databases, etc.).

Projects

Logical groupings of related deployments with shared tags and provider.

Deployments

Configured instances of templates with environment-specific variables.

Pipelines

Ordered sequences of deployments with output chaining between steps.

How it works

Template → Deployment → Plan → Approve → Apply → Outputs
  1. Pick a template — Choose from the curated template library or your own Terraform code in GitHub
  2. Configure a deployment — Set variables, region, and project through a step-by-step wizard
  3. Execute — Amnify runs terraform plan and shows you what will be created
  4. Review and approve — Inspect the plan output before anything is provisioned
  5. Apply — Amnify provisions the infrastructure and captures outputs (resource IDs, endpoints, etc.)

Supported providers

ProviderDeploy Support
AWSYes
AzureYes
GCPYes

Key features

Resource discovery

When configuring a deployment, Amnify can browse your existing cloud resources via dropdown selectors. Select existing VPCs, subnets, security groups, or resource groups — similar to the AWS or Azure console experience.

Pipeline output chaining

Create pipelines where the output of one deployment (e.g., a VPC ID) automatically feeds as input to the next deployment (e.g., an EC2 instance). Build complex multi-resource environments step by step.

Policy engine

Amnify evaluates your Terraform code against 1,000+ pre-configured security policies during the plan phase. Policies can warn, block, or allow deployments based on your configuration. See Policy Engine for details.

Sensitive variable encryption

Variables marked as sensitive are encrypted at rest and only decrypted at execution time — never exposed in the UI or logs.

Version pinning

Each deployment run is pinned to a specific Git commit SHA, ensuring reproducible deployments.

Prerequisites

To use Deploy, you need:
  1. A GitHub integration connected (for template access)
  2. A cloud provider integration (AWS, Azure, or GCP) connected