> 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.md).

# Policy Model

The building blocks of the Infrastructure Agent on every cloud: resources, their specs, results, and how they relate to each other.

The Infrastructure Agent Policy Model defines the resources the agent manages and how they relate to each other. Understanding this model helps you understand what the agent can do and why the creation flow follows the order it does.

## The Resource Hierarchy

The Infrastructure Agent organizes infrastructure as a hierarchy. Each level depends on the one above it:

**Network Baseline → Cluster Baseline → Environment → Resource Group → Kubernetes and Cloud Resources**

<figure><picture><source srcset="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-1598f6a2dbcdbc6ea88158fc891c96b444533954%2Fpolicy-model-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-0ef2b1ab55288c73e542f9c2bee74f5b3e6e7aff%2Fpolicy-model-light.png?alt=media" alt="Infrastructure Agent policy model: resource hierarchy and dependency relationships"></picture><figcaption></figcaption></figure>

A **Network Baseline** is the networking foundation everything else runs on. A **Cluster Baseline** runs a managed Kubernetes cluster inside that network. An **Environment** is a logical grouping that holds one or more **Resource Groups**.

A **Resource Group** is the isolation boundary. Every resource created inside it inherits its boundaries. It holds two kinds of children:

* **Kubernetes resources**: namespaces, workloads, jobs and cron jobs, ingress, config maps, secrets, storage, and Helm releases.
* **Cloud resources**: the managed services of the group's cloud, such as databases, storage and virtual machines.

**Faults** surface issues across any resource at any level of the hierarchy.

## On each cloud

You choose the cloud when you create a Network Baseline. Everything built on that network uses the same cloud.

| Resource             | AWS                                                                                                  | Azure                                                                                                                | Oracle Cloud (OCI)               |
| -------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
| **Network Baseline** | VPC with subnets, NAT and route tables                                                               | VNet in its own resource group, with a network security group per subnet and NAT gateways                            | VCN                              |
| **Cluster Baseline** | Amazon EKS                                                                                           | Azure Kubernetes Service (AKS)                                                                                       | Oracle Kubernetes Engine (OKE)   |
| **Resource Group**   | IAM role and policies, security groups, KMS key and EC2 key pair                                     | Azure resource group with a managed identity that its resources use                                                  | Compartment                      |
| **Cloud resources**  | S3, RDS, ElastiCache, SNS, SQS, Lambda, Secrets Manager, SSM parameters, EFS, MSK, ECR and EC2 hosts | Key Vault, Azure Database for PostgreSQL flexible server, Azure Managed Redis, storage accounts and virtual machines | None yet                         |
| **Plan**             | Hosted zones, ACM certificates and AMIs                                                              | Not available                                                                                                        | Not available                    |
| **Provisioned with** | CloudFormation                                                                                       | ARM deployments                                                                                                      | OCI Resource Manager (Terraform) |

Google Cloud (GCP) support is coming soon.

## Resource Lifecycle

Every resource follows the same status lifecycle. Each resource has a **Spec** tab showing what was requested, a **Result** tab showing what was provisioned, and a link to the underlying ticket that executed the work. Updates trigger a reconciliation — the agent handles only the delta, not a full teardown and rebuild.

<details>

<summary>View all lifecycle states</summary>

| Status                | Description                                                |
| --------------------- | ---------------------------------------------------------- |
| **Pending**           | Resource has been created and is waiting to be provisioned |
| **Provisioning**      | The AI agent is actively provisioning the resource         |
| **Ready**             | Resource is live and available                             |
| **Failed**            | Provisioning or an update encountered an error             |
| **Blocked**           | Waiting for user input before proceeding                   |
| **Awaiting Approval** | A change is pending approval before it is applied          |
| **DeProvisioning**    | Resource is being torn down                                |
| **DeProvisioned**     | Resource has been removed                                  |

</details>

## Resource Types

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Network Baseline</strong></td><td>The networking foundation: a VPC, VNet or VCN.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/network-baseline.md">Network Baseline</a></td></tr><tr><td><strong>Cluster Baseline</strong></td><td>A managed Kubernetes cluster (EKS, AKS or OKE) on top of a Network Baseline.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/cluster-baseline.md">Cluster Baseline</a></td></tr><tr><td><strong>Environment</strong></td><td>Logical grouping of Resource Groups inside a cluster.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/environment.md">Environment</a></td></tr><tr><td><strong>Plan</strong></td><td>AWS only. Account-level catalog of hosted zones, certificates, and AMIs.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/plan.md">Plan</a></td></tr><tr><td><strong>Faults</strong></td><td>Cross-resource issues detected across the hierarchy.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/faults.md">Faults</a></td></tr><tr><td><strong>Kubernetes Resources</strong></td><td>Namespaces, workloads, configs, secrets, and storage inside a Resource Group.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes.md">Kubernetes Resources</a></td></tr><tr><td><strong>Databases</strong></td><td>AWS RDS and ElastiCache inside a Resource Group.</td><td><a href="https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/databases.md">Databases</a></td></tr></tbody></table>


---

# 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.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.
