Templates
A Template is a reusable infrastructure blueprint. It defines a specific piece of cloud infrastructure that can be provisioned — for example, a Kubernetes cluster, a PostgreSQL database, a virtual network, or a complete multi-tier application stack.
The Amnify Template Library
To ensure your team can start deploying cloud infrastructure from day one, Amnify provides a comprehensive library of production-ready templates for all three supported cloud providers — Azure, AWS, and GCP. These templates cover the full range of modern infrastructure use cases:
| Category | Examples |
|---|---|
| Infrastructure | Virtual networks, compute clusters, Kubernetes environments, storage accounts |
| Data | Managed databases, data warehouses, streaming pipelines, analytics services |
| Application | Container deployments, web services, serverless functions, API gateways |
| Combinations | Multi-tier stacks that provision a complete environment — networking, compute, and data — in a single deployment |
This library is designed to address the most common infrastructure needs across engineering, data, and application teams so that your organization can begin provisioning cloud resources immediately, without any template authoring required.
A Spectrum of Customization
Amnify Deploy is designed to serve teams across the full range of infrastructure experience and customization needs:
| Approach | Who it's for | How it works |
|---|---|---|
| No-code | Teams that want production-ready cloud infrastructure without writing any code | Select a template from the provided library, fill in the configuration variables, and deploy |
| Low-code | Teams that need to adapt an existing template to fit a specific requirement | Modify a template's variables, add new inputs, or adjust its configuration in your GitHub repository |
| Full-code | Teams with specialized or complex requirements that go beyond available templates | Author entirely new templates in your GitHub repository, with direct support from the Amnify team |
If your organization has infrastructure requirements that are not covered by the provided template library, Amnify's team is available to work with you directly — whether that means guiding your engineers through template authoring or building custom templates on your behalf.
Your Templates, Your Repository
Regardless of their origin — provided by Amnify or authored by your team — all templates are stored in a GitHub repository owned by your organization. Amnify Deploy connects to that repository and syncs the templates from it. You have full control over your template library: templates are versioned and auditable via standard Git workflows, you can add a new template by adding a file to your repository, and you can modify an existing template by editing it in GitHub, pushing, and syncing. Your templates are not locked into the Amnify platform.
Amnify provides the template structure and convention that your files must follow, along with the execution engine that runs them. The content and design of your templates is entirely up to your team.
Template Variables
Every template exposes a set of variables — configurable inputs that are filled in at the time a Deployment is created. This is what makes a single template reusable across many different contexts.
| Property | Description |
|---|---|
| Name | The identifier used in the infrastructure definition |
| Label | The human-readable label shown in the Amnify interface |
| Required / Optional | Whether the variable must be provided before a deployment can be created |
| Sensitive | Marks the variable as secret (e.g., passwords, API keys); the value is never displayed after submission |
| Type | The data type: string, number, boolean, list, or map |
| Options | An optional predefined list of allowed values, presented as a dropdown in the UI |
Sensitive Variables
Variables marked as sensitive are treated with extra care: their values are stored securely and never displayed in the interface after submission, they are not shown in execution logs, and they can be updated via the Edit Deployment flow.
Cloud Resource Linking
Some variables are linked to live cloud resources. When creating a Deployment, the interface lets you browse and select an existing cloud resource for that variable — for example, selecting a resource group from your Azure subscription. This prevents manually copying and pasting resource identifiers.
Template Categories
Templates are organized into four categories to make browsing easier: Infrastructure, Data, Application, and Combinations. These categories apply to both the Amnify-provided library and any custom templates your team adds.
Syncing Templates
Amnify Deploy does not automatically pull changes from your GitHub repository. To make newly added or updated templates available, trigger a Sync from within the Amnify Deploy interface.
The sync process:
- Connects to your configured GitHub repository
- Reads all template files following the Amnify template structure
- Adds new templates and updates changed ones in the Amnify template library
- Makes them immediately available for creating new Deployments
Templates vs. Deployments
A Template is a blueprint; it does not represent deployed infrastructure. A Deployment is a specific instance of a Template applied to a real cloud environment with real configuration values.
One Template can produce many Deployments across different projects, environments, or cloud accounts.
Next Steps
- Deployments — learn how templates are turned into running infrastructure
- Using Templates guide — how to browse, select, add, and sync templates