> 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/aws-extension/aws-extension/policy-model/faults.md). # Faults Cross-resource issues detected across the AWS Extension hierarchy — surfaced with severity, context, and links to the originating ticket. Faults are issues detected by the platform across any resource in the AWS Extension — Networks, Clusters, Environments, workloads, or databases. They are surfaced centrally so teams can see and act on problems without hunting through individual resource views. Each Fault captures what went wrong, how severe it is, which resource is affected, and when it was detected. Where the fault originated from a ticket execution, a direct link to that ticket is included. ## Severity Levels | Severity | Description | | ------------ | ------------------------------------------------------------------------- | | **Info** | Informational — no immediate action required | | **Warning** | Something is degraded or suboptimal, but the resource is still functional | | **Error** | The resource has encountered a problem that requires attention | | **Critical** | A severe issue that may be causing an outage or data loss | ## Fault Details Each Fault includes: | Field | Description | | --------------- | ------------------------------------------------------------------------- | | **Message** | A description of the issue | | **Severity** | Info, Warning, Error, or Critical | | **Resource** | The resource type, ID, and name the fault is attached to | | **Detected At** | When the fault was first detected | | **Details** | Additional context or diagnostic information | | **Ticket** | A link to the ticket that triggered or detected this fault, if applicable | ## Where Faults Appear Faults are visible in the **Faults** view, which aggregates issues across all resource types in the workspace. Individual resource detail pages also surface any active faults attached to that specific resource. ## What's next Return to the [Policy Model overview](/docs/aws-extension/aws-extension/policy-model.md) to explore the full resource hierarchy. --- # 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/aws-extension/aws-extension/policy-model/faults.md?ask=&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.