Use Search to find resources within a tenancy, Console pages in services, and documentation within the Oracle Cloud Infrastructure getting started and user guides.
Search categorizes search results by resource, service, or documentation, helping you avoid navigating through menus, the latency associated with loading a long list of results onto a single page, or the inconvenience of viewing a long list that spans many pages. You can also filter results by criteria specific to the search category after results are found and sorted by category.
You might find it helpful to use Search to find related resources when creating or deleting another resource. For example, you might want to find what compartments already exist before creating a new one. Or, before you decide whether to delete a volume, you can use a query to verify that a backup exists.
Another benefit of Search is that you can find resources that require action. For example, you might want to delete terminated block volumes because you no longer need them and donโt want them to count against service limits. Or, you can search for all resources that match a specific naming scheme, in case you want to act on a category of associated resources. Sometimes, resources in a specific lifecycle state, such as databases in a failed state, require troubleshooting. With Search, you can quickly identify those resources and resolve problems. You can save frequent searches as resource collections to access the latest results more quickly later. Lastly, Search lets you use bulk actions to view work requests, manage tags, move resources, or delete resources.
Search can also help you find pages within the Console, even if you can't recall their location among services in the navigation menu. When you find a page, if you want to know more about its contents, you can use Search to find documentation to help you. For example, you might search for "create virtual cloud network" to read documentation about creating a virtual cloud network.
Search Categories and Ways to Search Them
To search for a resource, you can use a free text search based on keywords. You can also use structured resource query language to build an advanced query based on as little as a single resource attribute, such as the resource's creation date. Results for resource searches are limited to the tenancy and the selected regions.
To find a named page in the Console without knowing the service, to find help in the documentation, or to find an Oracle Cloud Infrastructure Marketplace listing, you can use a free text search. Advanced queries don't work for these types of searches.
Supported Resources ๐
Search supports queries for the Oracle Cloud Infrastructure services and resources listed in this section. The following table is updated as query support is added for more resources. You can see each resource's object reference for information about the resource, including its attributes. Sometimes, where indicated, a resource might not support all attributes for search. Often, services index only the required attributes for a particular resource. For current information about supported resources and resource attributes, use the ListResourceTypes API.
Note: Queries for the privateIp or publicIp attribute of a vnic will include the related instance, if one exists, and is running, in the query results.
Although you can use the query language to search fields and values for any supported attribute, query results only provide information about the following resource attributes:
Resource type
Oracle Cloud Identifier (OCID)
Compartment
Availability domain
Display name
Creation date and time
Lifecycle state
Tags (visible in the API only)
The preceding attributes are common to most Oracle Cloud Infrastructure resources. Their meaning is consistent across resource types, so they're provided by default for each result when you view a list of query results. Query results do not contain information specific to any resource type except where a matching search term appears. Meaning, you can query for volumes of a certain size. If there's a match, then the search result will display the attribute with the value that matches. In this example, in addition to the common attributes, the result also provides the Size attribute if that's where the match was found. You must view the details of a resource to see other resource-specific information.
Tip
If you use the Console, neither query results nor resource details will include either defined tags or free-form tags, due to display constraints. Any given resource might contain hundreds of tags. If you want to see tags, use the API to view resource details.
Required IAM Permissions ๐
The resources that you see in search or query results depend on the permissions you have in place for the resource type. You don't necessarily see results for every resource in the compartment or tenancy. For example, if your user account isn't associated with a policy that grants you the ability to, at a minimum, inspect the dbsystem resource type, then you canโt query for DB systems. (The verb inspect lets you list and get resources.) Instead, Search shows no results for queries of DB system resources.
Permissions and policy language applies to resources. Searching for pages across services in the Console or documentation requires no special permissions because they aren't resources. An administrator can't restrict access to search results for services or documentation.
For more information about policies, see How Policies Work. For information about the specific permissions required for the list API operation for a particular resource type, see the Policy Reference for the appropriate service.