Glossary
Quick definitions for the key terms used throughout Amnify Deploy documentation.
Apply
The second phase of the deployment lifecycle. After a Plan is approved, the apply step executes the planned changes and creates, modifies, or deletes cloud resources. See also: Plan, Approval Workflow.
Approval
A required human confirmation step in the deployment lifecycle. Amnify Deploy requires two approvals per execution: one for the Plan and one before the Apply. Neither can be skipped.
Deployment
A configured instance of a Template applied to a specific cloud environment with specific variable values. Executing a Deployment provisions real cloud infrastructure. See: Deployments.
Deployment Run
A single execution of a Deployment. Each time you execute or destroy a Deployment, a new Run is created. Runs capture the execution log, plan output, outputs, and status. See also: Run.
Destroy
An action that tears down the cloud resources managed by a Deployment. Destroy operations go through the same two-phase approval workflow as executions.
Execute
The action of provisioning (or updating) the cloud infrastructure defined by a Deployment. "Execute" and "Deploy" are used interchangeably in Amnify Deploy.
Integration
A configured connection between Amnify and a cloud account (Azure, AWS, or GCP). Integrations are set up by administrators and provide the credentials needed to provision infrastructure. See: Multi-Cloud Support.
Output
A value produced by a Deployment after a successful execution — for example, an endpoint URL, IP address, or resource ID. Outputs are shown on the Run detail page and are useful for connecting applications to the provisioned infrastructure.
Pipeline
An ordered sequence of Deployments that execute together, one after another, with a single trigger. Useful when infrastructure components have dependencies on each other. See: Pipelines.
Pipeline Run
A single execution of a Pipeline. It tracks the overall status of the Pipeline and the individual Deployment Runs triggered within it.
Plan
The first phase of the deployment lifecycle. Before any changes are made, Amnify Deploy generates a plan — a precise, read-only preview of every cloud resource that will be created, modified, or deleted. The plan must be reviewed and approved before execution proceeds. See: Approval Workflow.
Project
An organizational container that groups related Deployments together. Projects do not execute infrastructure themselves; they are a management and filtering tool. See: Projects.
Run
A single execution instance of a Deployment or Pipeline. Each Run captures its status, logs, plan output, outputs, and audit information (who triggered it, when). See: Monitoring Runs.
Sensitive Variable
A template variable marked as secret (e.g., a password or API key). Sensitive variable values are stored securely, never displayed after submission, and omitted from execution logs.
Sync
The action of pulling the latest templates from your GitHub repository into the Amnify template library. Sync is triggered manually. See: Using Templates.
Template
A reusable infrastructure blueprint stored in your organization's GitHub repository. Templates define what cloud resources can be provisioned and expose configurable variables. See: Templates.
Variable
A configurable input defined by a Template. Variables are filled in when creating a Deployment and determine the specific configuration of the provisioned infrastructure.