Deployment Target

Go up to Terms and Definitions

Discussion

A Deployment Target identifies a specific configured destination to which a Deployment can deliver an Infrastructure Environment.

A Deployment Target represents a concrete destination rather than a general technology, vendor, infrastructure category, or Deployment Platform.

For example:

identifies a Deployment PlatformAn identified AWS account, region, virtual private cloud, subnet set, resource boundary, and authorization context can constitute a Deployment TargetMicrosoft Azure identifies a Deployment PlatformAn identified Azure tenant, subscription, region, resource group, network boundary, and authorization context can constitute a Deployment TargetGoogle Cloud Platform identifies a Deployment PlatformAn identified Google Cloud organization, project, region, network boundary, resource boundary, and authorization context can constitute a Deployment TargetVMware vSphere identifies a Deployment PlatformAn identified vCenter instance, data center, cluster, resource pool, datastore set, network set, and authorization context can constitute a Deployment TargetRed Hat OpenShift Container Platform identifies a Deployment PlatformAn identified OpenShift cluster, project or namespace boundary, resource quota, network boundary, and authorization context can constitute a Deployment TargetBare-Metal Infrastructure identifies an infrastructure category that can provide a Deployment PlatformAn identified set of physical servers, networks, storage resources, management interfaces, and authorization boundaries can constitute a Deployment TargetA Deployment Target forms part of a Target Environment.

The Target Environment identifies the broader organizational, operational, security, compliance, connectivity, and physical context. The Deployment Target identifies the specific configured destination within that context to which the Deployment applies.

A Deployment Target can exist within a:

A Deployment Target record can identify:

A unique Deployment Target identifierA human-readable nameA descriptionThe Deployment PlatformThe platform, cloud, or infrastructure operatorThe Provider ImplementationThe account, tenant, subscription, project, cluster, site, or organizational boundaryThe geographic region, availability zone, facility, or physical locationThe network boundaryThe compute-resource boundaryThe storage-resource boundaryThe operational environmentThe connectivity classificationThe security classificationThe compliance profileThe supported processor architecturesThe supported operating systemsThe supported Machine ImagesThe supported Infrastructure BaselinesThe supported Deployment OperationsThe supported Deployment Validation capabilitiesThe supported Deployment Rollback capabilitiesThe authorized Dependency StoresThe authorized Artifact repositoriesThe authorized external resourcesThe credential or authorization referenceThe responsible owner or authorityThe approval statusThe availability statusThe lifecycle statusThe effective dateThe review or expiration dateThe associated ProvenanceThe associated TraceabilityA Deployment Description identifies the requirements of a proposed Deployment. A Deployment Target identifies the destination whose recorded capabilities, constraints, authorization, and status can be evaluated against those requirements.

A Deployment Target Catalog records the Deployment Targets available for discovery, evaluation, and selection.

Definition

specific configured destination, identified by its Deployment Platform, resource boundaries, operating conditions, and authorization context, to which a Deployment can deliver an Infrastructure Environment

Source

Dido Solutions, Crucible architecture and requirements terminologyDeploymentDeployment DescriptionDeployment PlatformTarget Environment

Note

A Deployment Platform identifies a platform type or technology. A Deployment Target identifies a specific configured destination that uses that Deployment Platform.

Multiple Deployment Targets can use the same Deployment Platform.

A Deployment Target can use more than one platform layer. For example, an OpenShift Deployment Target can use Amazon Web Services, Microsoft Azure, Google Cloud Platform, VMware vSphere, or Bare-Metal Infrastructure as its underlying platform.

A Deployment Target does not identify the Infrastructure Environment deployed to it:

The Deployment Target identifies the destinationThe Deployment Description identifies the Deployment requirementsThe Deployment creates or changes the Infrastructure EnvironmentThe presence of a Deployment Target in a Deployment Target Catalog does not by itself authorize its use. The Deployment Target record identifies its approval, availability, lifecycle, security, and compliance status.

A Deployment Target should reference an authorized credential-management mechanism rather than contain reusable credentials, private keys, passwords, or access tokens directly.

Example

An AWS Deployment Target identifies:

A Deployment Target identifierAmazon Web Services (AWS) as the Deployment PlatformAn AWS accountAn AWS regionA virtual private cloudThe permitted subnetsThe permitted availability zonesThe compute- and storage-resource boundariesThe identity role used for DeploymentThe authorized Dependency StoresThe authorized Artifact repositoriesThe supported Machine ImagesThe supported Infrastructure BaselinesThe security and compliance constraintsThe Provider ImplementationThe approval and availability statusThe responsible authorityCrucible compares a Deployment Description with the recorded capabilities and constraints of the Deployment Target before performing the Deployment.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.