Study guide

16.4 OCI Search with OpenSearch & Resource Search for Observability

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

16.4 OCI Search with OpenSearch & Resource Search for Observability

Key Takeaways Explain This Topic AI

OCI Search with OpenSearch is a managed service that handles security updates, upgrades, resizing, and scheduled backups of OpenSearch clusters.

OCI Search with OpenSearch clusters are reached through private endpoints in your VCN, on port 9200 for the OpenSearch API and port 5601 for OpenSearch Dashboards.

An OCI Search with OpenSearch cluster is read-only while it is patched and during most resize operations.

OCI Resource Search finds tenancy resources with free-text searches or a structured query language such as query instance resources where lifeCycleState = 'RUNNING' .

OCI Resource Search results include only resources that the user's IAM policies allow them to see.

Last updated: October 2026

Two Kinds of Search

Service What it searches Typical use

OCI Search with OpenSearch Your own data, indexed in managed OpenSearch clusters Application search, log analytics, observability dashboards

Resource Search (the Search service) OCI resources in your tenancy, Console pages, and documentation Inventory, cleanup, governance checks

The exam's observability objective includes OCI Search, so know what both do and when to use each.

OCI Search with OpenSearch

OCI Search with OpenSearch is a managed service for building search solutions based on OpenSearch . It searches large data sets and returns results in milliseconds, while OCI handles security updates, upgrades, resizing, and scheduled backups . OpenSearch Dashboards provide visualization, so the service is often used for log and event analytics as well as application search.

Cluster Node Types

Node type Role Minimum memory

Leader (formerly master) Manages cluster operations, tracks nodes, creates and deletes indices, allocates shards 20 GB

  • Data Stores data and handles search, indexing, and aggregation 20 GB
  • OpenSearch Dashboards Serves the Dashboards visualization interface 8 GB
  • Search Handles search operations and serves searchable snapshots Not applicable
  • Coordinator Stateless load balancer and query router for large clusters; holds no data Not applicable
  • Machine learning (ML) Runs ML Commons functions, such as models for semantic search Not applicable

Every cluster has at least one data node, leader node, and Dashboards node. Stable leader nodes are important for cluster health, which is why production clusters use multiple leaders.

Networking and Access

When you create a cluster, the service creates private endpoints in your VCN for the cluster API and for Dashboards, so all traffic stays inside the VCN.

Security rules must allow TCP 9200 (OpenSearch API) and TCP 5601 (Dashboards) from the clients that need them.

Administrators reach Dashboards from a laptop through OCI Bastion port forwarding or a jump host in the VCN. Applications in the VCN call port 9200 directly.

Users who create clusters need networking permissions in the compartment that holds the VCN and subnet, plus permissions on the OpenSearch resources: Allow group SearchOpenSearchAdmins to manage vnics in compartment network

  • Allow group SearchOpenSearchAdmins to manage vcns in compartment network
  • Allow group SearchOpenSearchAdmins to manage subnets in compartment network
  • Allow group SearchOpenSearchAdmins to use network-security-groups in compartment network
  • Allow group SearchOpenSearchAdmins to manage opensearch-family in compartment search

The opensearch-family aggregate covers opensearch-clusters , opensearch-cluster-backups , and opensearch-work-requests .

Patching, Resizing, and Backups

Oracle schedules patching during the third week of each month , with occasional unscheduled patches when needed. During patching the cluster is read-only : searches work, but writes fail. The more shards and indices, the longer the window.

The cluster is also read-only during horizontal resizes and most vertical resizes . The exception is increasing a data node's storage, which keeps the cluster writable.

Backups are created automatically and can be restored.

Design ingestion so that writers can buffer and retry , for example by sending events to OCI Streaming first and indexing from the stream. A short read-only window then delays indexing without losing data.

Limits and Quotas

Default limits for universal credit tenancies are 10 data nodes , 3 leader nodes , and 3 Dashboards nodes per region . Administrators can set compartment quotas on the opensearch family, such as data-node-count .

Notifications Integration

OpenSearch clusters can send alerts to OCI Notifications topics when a policy lets the cluster principal use topics: Allow any-user to manage ons-topics in tenancy where all {request.principal.type='opensearchcluster', request.resource.compartment.id='<compartment_ocid>'}

Where It Fits in an Observability Design

  • Need Better fit
  • Ad hoc search of OCI service and application logs with retention up to 180 days OCI Logging Search

Rich full-text search, custom dashboards, and long-lived indices over large event volumes OCI Search with OpenSearch

  • Metric charts and threshold alarms OCI Monitoring and Alarms
  • Product or document search inside an application OCI Search with OpenSearch

A common pattern sends logs through Connector Hub to Streaming , then into an OpenSearch ingestion pipeline that pulls from the stream and indexes events into the cluster.

Resource Search

Resource Search finds resources across a tenancy and selected regions. It also finds Console pages and documentation.

Free-text search matches keywords across supported resource types and attributes.

  • Structured queries use the Search query language: query instance resources where lifeCycleState = 'RUNNING'
  • query all resources where timeCreated > now - 7d
  • query group, user resources where displayName = 'administrator'
  • query instance resources return allAdditionalFields

Key syntax rules:

Queries start with query <resourceType> resources , and all searches every supported type. Individual resource types can be queried, but not family types.

where conditions use = (case-insensitive equals), == (case-sensitive equals), != , =~ (contains), and numeric or date comparisons. Combine them with && , || , or IN .

matching 'text' searches all indexed fields, and sorted by <field> asc|desc orders results; the default order is newest first.

union joins queries for different resource types that have different conditions.

IAM limits results. You see only the resources your policies allow you to inspect. Searching Console pages and documentation needs no permissions.

Using Resource Search for Operations

Find terminated or stopped resources that still count against limits or cost money.

List resources created in the last 24 hours after an incident.

Check which resources match a naming or tagging standard before cleanup.

Confirm that a backup exists before deleting a volume.

Loading diagram... Search Options in OCI Observability