Resources
Find any discovered cloud resource in the ZopNight inventory, drill into its children and details, and start, stop, or refresh it.
Every other feature in ZopNight (schedules, recommendations, reports, autoscaling) reads from one shared resource inventory. This page covers what gets discovered, how to find a resource, and what you can do with it.
Cloud Estate → Inventory: every resource with type, region, cost, purchase type, and status, with cascade filters and per-row start/stop.
Before you start
- At least one connected cloud account. See Cloud accounts.
- A role with
resource:viewto see the inventory. Your role’s scope decides which resources appear; see Scopes. - To start or stop resources: the cloud account connected at the Read + Write permission level. See Read-only vs read + write.
How it works
What gets discovered
When you connect a cloud account, ZopNight sweeps every region and pulls back the full resource list.
| Provider | Method | Coverage |
|---|---|---|
| AWS | Resource Explorer 2 + per-service providers | 81 resource types |
| GCP | Cloud Asset Inventory | 70 resource types |
| Azure | Resource Graph | 85 resource types |
| Databricks | Account API + workspace, or the Azure subscription | 6 types: workspaces, clusters, instance pools, SQL warehouses, jobs, model-serving endpoints |
| Snowflake | Account usage views + SHOW queries | 9 types: account, warehouses, databases, tables, materialized views, stages, pipes, users, resource monitors |
| Red Hat OpenShift | OpenShift Cluster Manager | 2 types: clusters and worker pools, plus Routes, DeploymentConfigs, BuildConfigs, ImageStreams, and Projects in the live workload view |
Your inventory lives under Cloud Estate → Inventory, with Table, Map, and Architecture tabs. Discovery re-runs about every six hours and picks up new or deleted resources automatically. You can also trigger a manual refresh from the cloud account. A manual refresh retries every provider, including any that were recently denied, so it picks up newly granted permissions.
Parent-child hierarchy
Many cloud resources are nested. A Kubernetes cluster has node groups, an ECS cluster has services, a container registry has repositories, and a Databricks workspace has clusters and SQL warehouses. ZopNight discovers these as parent-child trees up to three levels deep.
The default Inventory view shows parent resources only with a child-count badge. Click the badge to drill into the children. Breadcrumbs at the top of the page let you navigate back up.
Find a resource
Open Cloud Estate → Inventory
The Table tab lists parent resources with their type, region, tags, month-to-date cost, and status.
Search or filter
Search by name or UID, or narrow the list with the filters below. Use the Schedulable / Non-Schedulable toggle to see only what a schedule can act on.
Drill in
Click a child-count badge to open a parent’s children, and a row to open its detail drawer.
Filters
Filters are scoped to the current view, alongside a Schedulable / Non-Schedulable toggle. If you’re in the children view of an EKS cluster, the Type filter only shows resource types relevant to that cluster’s children (Deployments, StatefulSets, CronJobs, etc.).
| Filter | Behaviour |
|---|---|
| Cloud account | Grouped by provider with checkboxes. Tick multiple accounts to filter across them. Selecting every account under a provider sends a provider-wide filter; partial selections send per-account IDs. |
| Type | Resource types are grouped into nine categories: Compute, Kubernetes, Serverless, Database, Storage, Networking, Data & Analytics, ML & AI, and Messaging. Tick a category to select all types under it. |
| Status | Running, Stopped, or Transitioning. |
| Region | Narrowed automatically to regions the selected accounts actually use. |
Filters cascade. Selecting an account narrows the available types, statuses, and regions to what that account actually has. The dropdowns stay short, and you can’t filter yourself into an empty result.
Manual start and stop
Every resource that supports start/stop has a start/stop toggle in its row. Use it for one-off changes outside any schedule. Start/stop needs the cloud account to be connected with the Read + Write permission level. On a read-only account, ZopNight refuses the action before any cloud call.
Find the resource
Search by name or UID, or filter down to it.
Flip the toggle
Use the start/stop toggle in the row’s Actions column.
Confirm
ZopNight asks you to confirm before running the action. The triggered action shows up in the action status drawer so you can watch it process and complete.
Bulk actions
Tick the checkbox on multiple rows to bring up the bulk action banner. Bulk start/stop from the inventory sends one action per resource in parallel and does not follow any group’s start and stop order. To keep the order, use Start all or Stop all on a resource group, which runs through a four-worker pool and honours sequencing and delays.
Refreshing after infrastructure changes
If you just added a new cloud account, provisioned new infrastructure, or expect a resource to be there that isn’t, force a discovery refresh from the cloud account card. The action status drawer shows when discovery completes so you don’t act on stale data.
Resource details
Click any resource row to open the detail drawer. It shows:
| Section | What it shows |
|---|---|
| Metadata | Name, type, region, status, cloud account, instance type, size, tags. |
| Recent activity | Control-plane events ZopNight pulled from CloudTrail / Cloud Logging / Azure Activity Log. |
| Ownership | Who created the resource and who last modified it, with an active/departed badge resolved from your cloud identity directory. |
| Schedule | Which schedule (if any) is attached. |
| Recommendations | Open recommendations targeting this resource. |
| Cost | Current and historical cost. Each day uses billed cost where your billing data has a line for the resource, and rack rate where it doesn’t yet. |
Troubleshooting
A resource or resource type is missing
Open View Permissions on the account card in Settings → Cloud Accounts. Each resource type shows Granted, Denied, or Unknown, with the error for denied entries. After you grant the permission, trigger a manual refresh: scheduled discovery skips recently denied providers for up to a day, but a manual refresh retries all of them.
Start or stop is refused
The resource’s cloud account is read-only. ZopNight blocks manual, bulk, and scheduled start/stop on read-only accounts before any cloud call. Change the permission level to Read + Write on the account.
I can't find a snapshot or security group
These sit inside grouping folders such as “EBS Snapshots” or “Security Groups”. Drill into the folder, or search by name, which looks at every level.
Size and object count are empty for a new bucket
Size and count are filled in after the initial sweep. Give the first refresh a minute, then reload.