Infrastructure Projects in QuickInfra: Define Your Cloud Stack Once, Deploy Anywhere

Infrastructure Projects are the core of how QuickInfra handles cloud resource provisioning. Instead of writing and running Terraform yourself, you define your infrastructure requirements in the console and QuickInfra generates, validates, and applies the Terraform configuration on your behalf.

Creating an Infrastructure Project

An Infrastructure Project maps to a logical unit of your cloud — typically one environment (dev, staging, prod) of one application. You give it a name, bind it to a Cloud Account, select a region, and choose which services you need: VPC, EC2 instances, security groups, key pairs, load balancers, RDS, S3 buckets, and more.

Once you save the project configuration, QuickInfra generates the full Terraform code automatically. You can review the generated files in the Terraform Output tab before anything is applied.

The Five Actions

Every Infrastructure Project exposes five actions: Generate Terraform, View Terraform Plan, Create Infrastructure, Plan and Create, and Remove Infrastructure. These map directly to the standard Terraform workflow (init → plan → apply → destroy) but you never open a terminal. Each action streams its output in real time to the console log, with colour-coded status lines so you can see what's being created, what already exists, and what errored.

State Management

Terraform state is managed by QuickInfra automatically. State files are stored securely per project, versioned, and locked during active operations to prevent concurrent modifications. You don't need to configure an S3 backend, set up DynamoDB locking, or manage state files manually — the platform handles all of it.

Drift Detection

If someone makes a manual change to your AWS resources outside of QuickInfra (resizing an instance in the AWS console, adding a security group rule directly), the platform detects the drift on the next plan run and flags it. You can either accept the change (import it into state) or revert it by re-applying the project configuration. This keeps your actual infrastructure aligned with your declared configuration.

Multi-Environment Projects

You can duplicate an Infrastructure Project across environments using QuickInfra's Templates feature. Define your stack once as a template, then instantiate it for dev, staging, and production — each with its own variable overrides (instance sizes, replica counts, CIDR ranges). Changes to the template propagate to all instances with a review step before anything is applied.

When to Use Infrastructure Projects vs Deployment Projects

Infrastructure Projects are for the long-lived cloud resources — networks, compute, databases, storage. Deployment Projects are for the application layer on top of that infrastructure — container deployments, serverless functions, configuration pushes. Use both together for a complete end-to-end managed stack.