TABLE OF CONTENTS


Overview

The Aqua Inventory page displays all the resources that Aqua discovers. These resources include images, serverless functions, VMs, and other types of resources that are discovered on cloud accounts, and so on.


To see the Inventory screen, navigate to the mega menu, select Aqua Hub and from the left pane, select Inventory.



Supported resources

After cloud accounts are connected from the Integrations page, Aqua discovers the following AWS resources:

  • Container Images
  • EBS
  • ECR
  • ECS clusters
  • ECS services
  • EC2 instances

  • EKS node groups

  • Lambda functions

  • S3 buckets

As this feature is in preview mode, Aqua exposes only some of the resources in the Inventory page. Other types of resources will be added to the list in the future. If you do not find a resource in the list above and if you want us to add it, please contact Aqua.


Options in the Inventory page


You can search for any resource by using free text in the resource raw data.


Filters

You can apply different filters on all the resources to see the required. You can apply the following filter types:

  • Category
  • VM
  • Function
  • Container Images
  • Database
  • Storage
  • Other Cloud Resources
  • Other K8s Resources
  • Risk
  • Malware
  • Sensitive Data
  • Vulnerabilities
  • Cloud Misconfiguration
  • Severity: Critical through Negligible, and No issues

In the following example, Functions having Low-severity cloud misconfigurations are shown, by applying the respective filters.



FAQ on Inventory

Why can't I find a resource in the Inventory?

Ensure that you meet the following conditions to see the resources:

  • The service name of the list of supported resources exists.
  • After connecting your cloud accounts from the Aqua Hub Integrations page, please wait 24 hours to see resources and insights on the security findings detected in them. Aqua takes a maximum of a few hours to discover and scan the resources for the first scan. This scan time varies depending on the number of workloads and size of the resources in your cloud account. Subsequent scans will generally take less time.