> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/environment.md).

# Environment

A deployment boundary inside a cluster, isolating teams, applications, or stages from each other.

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

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

## Spec

| Field       | Description                                                                                                                                                                |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cluster** | The Cluster Baseline this Environment lives inside                                                                                                                         |
| **Plans**   | AWS only. 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

On AWS, 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**.

{% hint style="warning" %}
An Environment cannot be deprovisioned while workloads or databases are running inside it. Deprovision all child resources first.
{% endhint %}

## What's next

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

* [Kubernetes Resources](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes.md) — Namespaces, Workloads, Configs, and Storage
* [Databases](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/databases.md) — RDS and ElastiCache instances on AWS


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/environment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
