Environment

A deployment boundary inside a cluster — isolated with its own IAM roles, security groups, and KMS keys.

An Environment is a deployment boundary inside an EKS Cluster. It provides isolation between teams, applications, or stages (development, staging, production) by provisioning a dedicated set of AWS resources: security groups, IAM roles, and KMS encryption keys.

All workloads, Kubernetes resources, and databases created inside an Environment inherit its IAM and network boundaries.

Spec

Field	Description
Cluster	The Cluster Baseline this Environment lives inside
Plans	One or more Plans to associate with this Environment. Plans provide hosted zones, ACM certificates, and AMI references available to resources in the Environment

Result

Once provisioned, the Environment result includes:

Field	Description
Security Groups	Dedicated security groups controlling inbound and outbound traffic for resources in this Environment
IAM Roles	IAM roles scoped to this Environment for workloads and service accounts
KMS Keys	Encryption keys for secrets and storage resources in this Environment
Resource Groups	A count of the sub-resources (Kubernetes resources, databases, etc.) provisioned inside the Environment

Navigation

The Environment detail view provides a full resource tree in the left navigation — covering Kubernetes resources (Namespaces, Workloads, Configs, Storage) and Cloud Resources (Databases, Hosts, Networks). Each sub-resource has its own list view, create form, and detail page.

Dependencies

An Environment requires a Cluster Baseline.

An Environment cannot be deprovisioned while workloads or databases are running inside it. Deprovision all child resources first.

What's next

With an Environment ready, you can create resources inside it:

• Kubernetes Resources — Namespaces, Workloads, Configs, and Storage

• Databases — RDS and ElastiCache instances