Infrastructure Templates: Define Your Cloud Stack Once, Reuse It Forever

Most engineering teams have a "standard stack" — the set of cloud resources that every new project or environment needs. The first time you set this up it takes days. The tenth time it should take minutes. QuickInfra's Infrastructure Templates make that possible.

What Is an Infrastructure Template?

An Infrastructure Template in QuickInfra is a reusable configuration blueprint for a cloud stack. It defines the resources, their relationships, and the variables that can be customised per deployment (instance type, CIDR ranges, region, environment tag). Think of it as a parameterised Terraform module, but one you manage in the console without writing HCL.

Creating a Template

Go to Templates → Infrastructure → New Template. You can create a template from scratch by adding resources from the component library, or save an existing Infrastructure Project as a template — useful for capturing a stack you've already built and tested in production. Variables are declared with types and default values, with a description that appears in the deployment form.

Deploying From a Template

Select the template from the library and fill in the variable values for this specific deployment. QuickInfra generates the Terraform configuration with your variable values substituted in, and you proceed with the standard plan → apply workflow. A new staging environment that previously took a day of setup can be ready in fifteen minutes.

Template Library

QuickInfra ships a library of pre-built templates covering common AWS architectures:

• Single EC2 with VPC
• EC2 with Application Load Balancer
• EC2 with RDS (PostgreSQL and MySQL)
• ECS Fargate service
• Static website (S3 + CloudFront)
• Three-tier web application (ALB + EC2 Auto Scaling + RDS)

Each template follows AWS Well-Architected Framework principles. You can use them directly or fork them as the starting point for your own custom templates.

Version Control for Templates

Templates are versioned. Existing Infrastructure Projects deployed from a template are not automatically updated when the template changes — they remain on the version they were deployed with. You can choose to upgrade a project to a newer template version through a migration wizard that shows exactly what will change before you apply.

Sharing Templates Across Teams

Templates are organisation-scoped. Any template created by one team member is available to all users in the organisation with the appropriate access level. This enables platform engineering teams to publish approved, standardised infrastructure patterns that application teams consume — without the application teams needing to understand the underlying Terraform.