Infrastructure Environment [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Infrastructure Environment ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]

===== Discussion =====

An Infrastructure Environment is the bounded collection of infrastructure resources, configuration values, relationships, and constraints required to provide an identified operational or development context.

An Infrastructure Environment describes the infrastructure context as a whole rather than an individual resource within that context.

An Infrastructure Environment may include:

  * Compute resources
  * Storage resources
  * Network resources
  * Security controls
  * Identity and access services
  * Platform services
  * Configuration values
  * Relationships among resources
  * Applicable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]
  * Operational constraints
  * Environment-specific parameters

Examples of Infrastructure Environments include development, integration, test, staging, production, training, classified, unclassified, connected, disconnected, and [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].

An Infrastructure Environment differs from an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]:

  * The Infrastructure Environment is the infrastructure context being described, created, operated, or evaluated
  * The Infrastructure Configuration is the information used to represent or control the desired state of the Infrastructure Environment

===== Definition =====

//environment comprising an identified collection of infrastructure resources, configuration values, relationships, and constraints established for a defined operational or development purpose//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

===== Note =====

An Infrastructure Environment may exist as a planned desired state, a deployed environment, or an observed operational state.

The term does not require a particular deployment technology, cloud provider, virtualization platform, container platform, operating system, or physical infrastructure.

An Infrastructure Environment may inherit configuration from another Infrastructure Environment or may use a shared [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]], but the environment remains independently identifiable.

===== Example =====

A production Infrastructure Environment may include compute instances, storage volumes, network segments, access controls, monitoring services, configuration values, and applicable Baseline references required to operate an application in a controlled production context.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>