|
| 1 | +--- |
| 2 | +title: Find Deleted Resources History |
| 3 | +sidebar_label: Find Deleted Resources History |
| 4 | +--- |
| 5 | + |
| 6 | +# Find Deleted Resources History |
| 7 | + |
| 8 | +In this guide, you will learn how to: |
| 9 | +- Use the Guardrails UI to access historical data for resources that have been deleted from Guardrails. |
| 10 | + |
| 11 | +When a resource is deleted from Guardrails, the [resource](/guardrails/docs/reference/glossary#resource) itself is no longer visible in the console. However, its historical activity remains accessible via the **Activity** tab. This information is particularly useful for troubleshooting, auditing, and debugging. |
| 12 | + |
| 13 | +## Prerequisites |
| 14 | + |
| 15 | +- **Turbot/Operator** permissions at the Turbot resource level. |
| 16 | +- Familiarity with the Guardrails console. |
| 17 | + |
| 18 | +## Step 1: Navigate to the Resources Tab |
| 19 | + |
| 20 | +Log in to the Guardrails console using valid credentials and select the **Resources** tab from the top menu. |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +## Step 2: Navigate to the Region |
| 25 | + |
| 26 | +Drill down into the region where the deleted resource previously existed. For example, navigate to `us-east-2` if the resource was located there. Select the **Activity** tab to view historical events. |
| 27 | + |
| 28 | + |
| 29 | + |
| 30 | +## Step 3: Configure Activity Filters |
| 31 | + |
| 32 | +Use the following filters to narrow your search and include relevant activity history: |
| 33 | + |
| 34 | +**Descendant**: Enable the `Descendant` checkbox on the left. This allows the search to include all child resources under the selected parent. |
| 35 | + |
| 36 | +  |
| 37 | + |
| 38 | +**Resource Type**: From the right-hand filter pane, open the `Resource Type` dropdown and select the appropriate resource type. |
| 39 | + > For demonstration purposes, this guide uses `AWS > S3 > Bucket` as an example. You should select the resource type relevant to your use case. |
| 40 | +
|
| 41 | +  |
| 42 | + |
| 43 | +**Type**: Select both **Control** and **Resource** under the `Type` dropdown to view lifecycle changes and control evaluations. |
| 44 | + |
| 45 | +  |
| 46 | + |
| 47 | +**Timestamp**: Use the `Timestamp` dropdown to define a date range if you know roughly when the deletion occurred. |
| 48 | + |
| 49 | +  |
| 50 | + |
| 51 | +## Step 4: Search Deleted Resource |
| 52 | + |
| 53 | +Enter the resource name (or a keyword) into the **Search Box** to locate any matching historical entries. The results may include the full activity history of the deleted resource, including creation events, configuration and policy changes, control evaluations, and the deletion event itself. |
| 54 | + |
| 55 | + Select the entry to view detailed information. |
| 56 | + |
| 57 | + |
| 58 | + |
| 59 | +## Step 5: Review Deleted Resource Data |
| 60 | + |
| 61 | +The resource data is displayed under the Deleted Resource section, which can be used to understand the context and impact of the removal or to capture any required information for auditing or troubleshooting. |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | +If you encounter any further issues, please [Open Support Ticket](https://support.turbot.com) and attach the relevant information to assist you more efficiently. |
| 66 | + |
| 67 | +- The full resource name or ARN (if known). |
| 68 | +- The region and approximate deletion time. |
| 69 | +- A brief description of what you're trying to find and any filters you applied. |
0 commit comments