{"id":908,"date":"2026-04-16T15:53:38","date_gmt":"2026-04-16T15:53:38","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-advisor-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-governance-and-administration\/"},"modified":"2026-04-16T15:53:38","modified_gmt":"2026-04-16T15:53:38","slug":"oracle-cloud-advisor-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-governance-and-administration","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-advisor-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-governance-and-administration\/","title":{"rendered":"Oracle Cloud Advisor Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Governance and Administration"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Governance and Administration<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Oracle Cloud <strong>Cloud Advisor<\/strong> is a Governance and Administration service that helps you <strong>continuously improve your Oracle Cloud Infrastructure (OCI) environment<\/strong> by surfacing recommendations across common pillars like cost, performance, availability, and security (the exact set of pillars and recommendation types depends on OCI\u2019s current implementation\u2014verify in official docs).<\/p>\n\n\n\n<p>In simple terms: <strong>Cloud Advisor looks at what you have deployed in Oracle Cloud and suggests what to change<\/strong> to save money, reduce risk, and improve reliability.<\/p>\n\n\n\n<p>In more technical terms: Cloud Advisor aggregates signals from your OCI tenancy\u2014resource configuration, usage patterns, telemetry, and OCI service metadata\u2014and generates <strong>recommendations<\/strong> that are <strong>scoped to compartments<\/strong> and governed by OCI IAM policies. Teams typically use it as part of an operational governance loop: review recommendations, validate impact, remediate using safe change practices, and track outcomes over time.<\/p>\n\n\n\n<p>The core problem it solves is operational drift: as environments grow, it becomes easy to accumulate <strong>idle resources, mis-sized services, suboptimal high-availability patterns, and security weaknesses<\/strong>. Cloud Advisor provides a practical, centralized way to detect improvement opportunities and prioritize them.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (important): Oracle Cloud documentation and the OCI Console use product names that can evolve. In some OCI SDK\/CLI surfaces, the underlying recommendation APIs may appear under a different service name (for example, \u201cOptimizer\u201d in some tooling). Treat <strong>Cloud Advisor<\/strong> as the primary product experience in this tutorial, and <strong>verify the current API\/service naming in official docs<\/strong> if you plan to automate.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Cloud Advisor?<\/h2>\n\n\n\n<p><strong>Official purpose (what it\u2019s for)<\/strong><br\/>\nCloud Advisor is designed to provide <strong>actionable recommendations<\/strong> to help you operate OCI resources according to Oracle-recommended practices. It aims to reduce waste, strengthen security posture, improve performance efficiency, and enhance availability\u2014without requiring you to manually inspect every service across every compartment.<\/p>\n\n\n\n<p><strong>Core capabilities (what it does)<\/strong>\n&#8211; Displays <strong>recommendations<\/strong> for OCI resources (coverage varies by resource type and region\u2014verify in official docs).\n&#8211; Organizes recommendations by <strong>category\/pillar<\/strong>, <strong>compartment<\/strong>, and <strong>status<\/strong> (for example: active vs dismissed\u2014exact statuses vary).\n&#8211; Provides <strong>context<\/strong> per recommendation: impacted resources, reasoning, and suggested remediation.\n&#8211; Often provides <strong>estimated benefit<\/strong> where applicable (for example, potential cost savings for cost-related recommendations\u2014availability varies).\n&#8211; Supports a governance workflow: review, triage, remediate, and track.<\/p>\n\n\n\n<p><strong>Major components (how it\u2019s structured)<\/strong>\n&#8211; <strong>Recommendation inventory<\/strong>: the list of current recommendations.\n&#8211; <strong>Recommendation details<\/strong>: impacted resource(s), reasoning, and suggested actions.\n&#8211; <strong>Scoping &amp; filtering<\/strong>: by compartment, category, and status.\n&#8211; <strong>Lifecycle controls<\/strong>: mechanisms like dismissing\/suppressing a recommendation (feature names vary; verify).\n&#8211; <strong>(Optional) APIs\/SDK\/CLI<\/strong>: programmatic retrieval and tracking of recommendations (verify the current API group name in official docs).<\/p>\n\n\n\n<p><strong>Service type<\/strong>\n&#8211; A <strong>governance and advisory<\/strong> service (not a deployment runtime, not a data plane).\n&#8211; Primarily <strong>read\/analysis<\/strong> plus workflow metadata (dismissal\/status), with remediation typically performed by changing the underlying OCI resources.<\/p>\n\n\n\n<p><strong>Scope model (tenancy\/compartment)<\/strong>\n&#8211; Cloud Advisor is effectively <strong>tenancy-aware<\/strong> but operationally <strong>compartment-scoped<\/strong>:\n  &#8211; Recommendations apply to resources that live in compartments.\n  &#8211; Visibility is controlled through <strong>OCI IAM policies<\/strong> (who can view recommendations for which compartments).<\/p>\n\n\n\n<p><strong>Regional\/global behavior<\/strong>\n&#8211; The Cloud Advisor UI is accessed from the OCI Console, while recommendations may be generated from service signals that are region-specific. In practice:\n  &#8211; You will commonly filter by <strong>region<\/strong> and <strong>compartment<\/strong> when investigating recommendations.\n  &#8211; Recommendation coverage can differ per region and per service.<\/p>\n\n\n\n<p><strong>How it fits into the Oracle Cloud ecosystem<\/strong>\nCloud Advisor complements other Governance and Administration services and operational tooling:\n&#8211; <strong>IAM<\/strong> (who can see and change what)\n&#8211; <strong>Compartments<\/strong> and <strong>tagging<\/strong> (organization and ownership)\n&#8211; <strong>Audit<\/strong> (tracking change)\n&#8211; <strong>Monitoring<\/strong> (telemetry and dashboards)\n&#8211; <strong>Cost Management \/ Cost Analysis<\/strong> (spend visibility)\n&#8211; <strong>Cloud Guard<\/strong> (security posture management; distinct from Cloud Advisor but often used together)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Cloud Advisor?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduce cloud spend<\/strong> by identifying unused or underutilized resources and configuration inefficiencies.<\/li>\n<li><strong>Improve financial governance<\/strong> with repeatable review cycles and evidence-based recommendations.<\/li>\n<li><strong>Accelerate decision-making<\/strong>: teams spend less time hunting for issues across consoles and services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Helps uncover common technical gaps:<\/li>\n<li>Over-provisioned compute\/database shapes<\/li>\n<li>Idle resources<\/li>\n<li>Misaligned storage tiers<\/li>\n<li>Non-HA patterns where HA is expected<\/li>\n<li>Provides a centralized view that is difficult to replicate reliably with ad-hoc scripts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establishes an <strong>operational hygiene backlog<\/strong>:<\/li>\n<li>Review cadence (weekly\/monthly)<\/li>\n<li>Ownership mapping (via compartments\/tags)<\/li>\n<li>Standard remediation playbooks<\/li>\n<li>Helps platform teams scale governance across many projects.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Surfaces security-related improvement opportunities (exact types vary).  <\/li>\n<li>Supports audit-friendly operations: recommendations can be reviewed, triaged, and remediated with change controls and OCI Audit logs capturing the actual changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identifies opportunities to right-size or reconfigure for better performance efficiency (where supported).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Cloud Advisor<\/h3>\n\n\n\n<p>Choose Cloud Advisor when you:\n&#8211; Run multiple environments\/compartments and need consistent optimization signals.\n&#8211; Want a low-friction way to find cost\/risk reduction opportunities.\n&#8211; Need a governance-friendly process for continuous improvement across teams.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Cloud Advisor is not a replacement for:\n&#8211; <strong>Real-time monitoring\/alerting<\/strong> (use OCI Monitoring, alarms, Logging)\n&#8211; <strong>Security threat detection and response<\/strong> (use Cloud Guard + SIEM patterns)\n&#8211; <strong>Capacity\/load testing<\/strong> (use application performance engineering)\n&#8211; <strong>Custom compliance engines<\/strong> where you need bespoke controls beyond what Cloud Advisor checks<\/p>\n\n\n\n<p>If you need fully customized policy-as-code checks and enforcement, you may use Cloud Advisor as an input, but not as the only mechanism.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Cloud Advisor used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Finance, healthcare, and public sector (cost control + auditability)<\/li>\n<li>SaaS and tech (continuous optimization at scale)<\/li>\n<li>Retail and media (seasonality and cost efficiency)<\/li>\n<li>Manufacturing and logistics (mixed workloads and long-lived environments)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Platform engineering \/ cloud center of excellence (CCoE)<\/li>\n<li>DevOps\/SRE teams<\/li>\n<li>Security engineering and compliance teams<\/li>\n<li>FinOps \/ cost governance teams<\/li>\n<li>Application teams that own their compartments<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Web applications (compute, load balancing, autoscaling patterns)<\/li>\n<li>Microservices and Kubernetes (node sizing, idle clusters\u2014coverage varies)<\/li>\n<li>Databases (performance and cost sizing patterns\u2014coverage varies)<\/li>\n<li>Analytics pipelines (storage usage patterns)<\/li>\n<li>Dev\/test estates (frequent source of idle resources)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multi-compartment enterprise landing zones<\/li>\n<li>Multi-region setups (availability recommendations may become relevant)<\/li>\n<li>Shared services models (networking, security, logging centralized)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: focus on risk reduction, HA improvements, long-lived resource optimization.<\/li>\n<li><strong>Dev\/test<\/strong>: focus on eliminating idle resources and enforcing cleanup cycles.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic, commonly adopted Cloud Advisor patterns. Exact recommendation availability depends on OCI\u2019s supported resource types\u2014<strong>verify in official docs<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Identify idle or underutilized compute instances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Instances run 24\/7 but average utilization is low.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> It can highlight candidates for rightsizing or shutdown schedules.<\/li>\n<li><strong>Scenario:<\/strong> A dev environment uses VM instances continuously; Cloud Advisor flags low utilization so the team moves to smaller shapes or schedules off-hours shutdown.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Detect unattached storage that still incurs cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Block volumes or boot volumes remain after instance termination.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> It can surface orphaned storage resources to delete or reattach.<\/li>\n<li><strong>Scenario:<\/strong> A project tears down test instances but leaves volumes behind; Cloud Advisor highlights volumes with no attachments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Consolidate over-provisioned database resources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Database shapes are larger than required and costly.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Recommendations can indicate resizing opportunities (where supported).<\/li>\n<li><strong>Scenario:<\/strong> A staging database runs on a production-sized configuration; Cloud Advisor recommends a smaller shape.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Improve high availability for critical services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Workloads run in a single fault domain\/AD pattern when higher resilience is needed.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> It can point out non-HA configurations relative to best practices (where supported).<\/li>\n<li><strong>Scenario:<\/strong> A customer-facing service runs on a single instance; Cloud Advisor recommends using multiple instances behind a load balancer.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Reduce unused public IP exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Public IPs remain allocated and increase attack surface (and may incur cost depending on OCI policy\/SKU).<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> It can highlight resources that can be released or reconfigured.<\/li>\n<li><strong>Scenario:<\/strong> A team migrates to private endpoints but forgets to release old public IPs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Improve backup\/retention posture<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Critical data lacks appropriate backups or lifecycle policies.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> It can identify missing resilience configurations (where supported).<\/li>\n<li><strong>Scenario:<\/strong> A database is running without automated backups configured; Cloud Advisor recommends enabling backups.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Optimize load balancer or gateway usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Load balancers exist but serve little\/no traffic; gateways are mis-sized or unnecessary.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Highlights potential cost reductions and architectural simplification.<\/li>\n<li><strong>Scenario:<\/strong> A blue\/green migration leaves an old load balancer in place; Cloud Advisor flags it as underutilized.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Find networking configurations that need review<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Network configuration drift creates inefficiency or risk.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Some recommendations can highlight configuration improvements (coverage varies).<\/li>\n<li><strong>Scenario:<\/strong> A compartment contains old VCN components from an abandoned project; Cloud Advisor helps prioritize cleanup.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Establish a monthly FinOps review board backed by recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Cost reviews are manual and inconsistent.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Provides a stable list of actions to discuss, assign, and track.<\/li>\n<li><strong>Scenario:<\/strong> FinOps exports Cloud Advisor recommendations monthly and assigns owners by compartment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Standardize governance across many compartments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Different teams follow different operational hygiene standards.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> A central view helps enforce consistency.<\/li>\n<li><strong>Scenario:<\/strong> A platform team reviews Cloud Advisor weekly across all product compartments and opens tickets.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Support pre-production readiness checks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Performance and availability gaps go unnoticed until incident time.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Acts as a pre-flight checklist input (not a guarantee).<\/li>\n<li><strong>Scenario:<\/strong> Before launch, a team reviews Cloud Advisor and remediates availability-related recommendations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Feed automation or ITSM workflows (where APIs are available)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Recommendations are discovered but not tracked.<\/li>\n<li><strong>Why Cloud Advisor fits:<\/strong> Export\/API-based ingestion supports ticketing and reporting.<\/li>\n<li><strong>Scenario:<\/strong> A script pulls recommendations weekly and creates Jira\/ServiceNow tickets (verify API availability and naming).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Feature availability can change; treat the list as \u201ccore intent\u201d and <strong>confirm details in the current OCI Cloud Advisor documentation<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Centralized recommendations dashboard<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lists recommendations across supported OCI services\/resources.<\/li>\n<li><strong>Why it matters:<\/strong> You avoid checking each service manually.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster identification of \u201ceasy wins\u201d like unused resources.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Not all OCI services are covered; some recommendations appear only after sufficient telemetry is collected.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Categorization by optimization pillar<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Groups recommendations by themes such as cost, performance, availability, and security (exact categories vary).<\/li>\n<li><strong>Why it matters:<\/strong> Different teams can focus on what they own (FinOps vs SRE vs Security).<\/li>\n<li><strong>Practical benefit:<\/strong> Easier prioritization and routing.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Categories are not a substitute for formal risk scoring; treat them as guidance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Compartment-based scoping and filtering<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lets you view recommendations for selected compartments (and often their children).<\/li>\n<li><strong>Why it matters:<\/strong> OCI environments are usually compartment-structured for governance.<\/li>\n<li><strong>Practical benefit:<\/strong> You can align recommendations to ownership boundaries.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Cross-compartment architectures may require broader review context.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Recommendation details and impacted resources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Shows the resource(s) tied to a recommendation and why it was generated.<\/li>\n<li><strong>Why it matters:<\/strong> Teams need evidence before making changes.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster validation and remediation planning.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Some recommendations are high-level; you may need to inspect the resource configuration and metrics yourself.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Lifecycle controls (dismiss\/suppress\/track)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows managing recommendation workflow state (for example, dismissing noisy items).<\/li>\n<li><strong>Why it matters:<\/strong> Reduces repeated triage of accepted risk.<\/li>\n<li><strong>Practical benefit:<\/strong> A cleaner operational backlog.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Dismissing does not fix the underlying issue; treat dismissals as documented risk acceptance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Estimated savings or impact (where available)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides potential cost savings or impact estimates for some recommendations.<\/li>\n<li><strong>Why it matters:<\/strong> Helps prioritize changes with measurable ROI.<\/li>\n<li><strong>Practical benefit:<\/strong> Supports FinOps reporting and business justification.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Estimates are not invoices. Validate using Cost Analysis and usage reports.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Integration with OCI IAM for governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Uses OCI policies to control who can see recommendations and who can remediate resources.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents unauthorized viewing of sensitive resource metadata.<\/li>\n<li><strong>Practical benefit:<\/strong> Aligns with least privilege and separation of duties.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> If users can view recommendations but not manage resources, remediation requires coordination.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) (Optional) Programmatic access for reporting\/automation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables pulling recommendations via SDK\/CLI\/API (naming may differ\u2014verify in official docs).<\/li>\n<li><strong>Why it matters:<\/strong> Enterprise workflows often require centralized reporting and ticket creation.<\/li>\n<li><strong>Practical benefit:<\/strong> Repeatable and auditable processes.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> API permissions and endpoints may be different from the console experience; confirm supported operations.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level service architecture<\/h3>\n\n\n\n<p>At a high level, Cloud Advisor:\n1. Observes your OCI environment using signals from OCI services (configuration metadata, usage\/telemetry, service events).\n2. Runs rule\/analysis logic to identify improvement opportunities.\n3. Stores the outputs as recommendation objects scoped to compartments\/resources.\n4. Presents them in the OCI Console (Cloud Advisor UI), and optionally through APIs.\n5. You remediate by changing the underlying resources (delete, resize, reconfigure, enable features, etc.).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Data flow:<\/strong> OCI services \u2192 telemetry\/metadata \u2192 Cloud Advisor analysis \u2192 recommendations store \u2192 console\/API.<\/li>\n<li><strong>Control flow:<\/strong> Users (via IAM) \u2192 view recommendations \u2192 implement changes in the target services \u2192 Cloud Advisor refresh cycle updates recommendation state.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IAM:<\/strong> controls who can view recommendations and who can modify underlying resources.<\/li>\n<li><strong>Compartments &amp; tagging:<\/strong> used for scoping, ownership, chargeback\/showback.<\/li>\n<li><strong>Monitoring:<\/strong> provides metrics that may influence rightsizing\/underutilization signals.<\/li>\n<li><strong>Audit:<\/strong> records remediation actions taken in OCI services.<\/li>\n<li><strong>Cost Management (Cost Analysis \/ usage reports):<\/strong> validates realized savings after remediation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>Cloud Advisor depends on the existence and correct functioning of:\n&#8211; Target OCI services (Compute, Storage, Networking, Database, etc.)\n&#8211; Telemetry availability (metrics\/configuration data)\n&#8211; IAM and compartment structure<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Uses standard OCI identity:<\/li>\n<li>Users authenticate to OCI Console\/CLI.<\/li>\n<li>Authorization is enforced through IAM policies.<\/li>\n<li>Cloud Advisor itself typically does not require agents installed on instances; it relies on OCI control plane data.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor is part of the OCI control plane. You access it via the OCI Console over HTTPS.<\/li>\n<li>No VCN configuration is usually required to <em>view<\/em> recommendations.<\/li>\n<li>Remediation changes may involve VCN security rules, instance reconfiguration, etc., which must follow your network governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Audit<\/strong> to track who changed resources in response to recommendations.<\/li>\n<li>Use <strong>OCI Monitoring<\/strong> to validate performance impacts after rightsizing.<\/li>\n<li>Use <strong>Cost Analysis<\/strong> to validate savings (don\u2019t rely only on estimated impact).<\/li>\n<li>Establish a governance process: ownership, SLAs for review, and change windows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (conceptual)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  A[OCI Services\\nCompute\/Storage\/Network\/DB] --&gt; B[Telemetry &amp; Metadata]\n  B --&gt; C[Cloud Advisor\\nRecommendation Engine]\n  C --&gt; D[Recommendations]\n  D --&gt; E[OCI Console\\nCloud Advisor UI]\n  E --&gt; F[Engineer\/FinOps\/SRE]\n  F --&gt; G[Remediation in OCI Services]\n  G --&gt; A\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (enterprise governance loop)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Tenancy[OCI Tenancy]\n    subgraph LandingZone[Compartments \/ Landing Zone]\n      C1[Prod Compartments]\n      C2[Non-Prod Compartments]\n      C3[Shared Services Compartment]\n    end\n\n    S1[OCI Services\\nCompute\/DB\/Network\/Storage] --&gt; CA[Cloud Advisor\\nRecommendations]\n    CA --&gt; UI[OCI Console]\n    CA --&gt; API[Optional: API\/SDK\/CLI\\n(verify naming in docs)]\n    UI --&gt; Teams[App Teams \/ SRE \/ Security \/ FinOps]\n\n    API --&gt; Report[Central Reporting\\nDashboards\/Exports]\n    Report --&gt; ITSM[Ticketing \/ Change Mgmt\\n(Jira\/ServiceNow etc.)]\n\n    Teams --&gt; Change[Change Implementation\\nin OCI Services]\n    Change --&gt; Audit[OCI Audit Logs]\n    Change --&gt; Mon[OCI Monitoring Metrics]\n    Change --&gt; Cost[OCI Cost Analysis]\n  end\n\n  Audit --&gt; Review[Governance Review\\nWeekly\/Monthly]\n  Mon --&gt; Review\n  Cost --&gt; Review\n  Review --&gt; CA\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<p>Before you start working with Cloud Advisor, confirm the following.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy\/account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Oracle Cloud (OCI) tenancy<\/strong>.<\/li>\n<li>Access to the <strong>OCI Console<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM<\/h3>\n\n\n\n<p>You need permissions to:\n&#8211; <strong>View recommendations<\/strong> in Cloud Advisor for the compartments you care about.\n&#8211; <strong>Inspect and modify<\/strong> the underlying resources to implement remediations (Compute, Block Volume, Network, Database, etc.).<\/p>\n\n\n\n<p>Because OCI IAM policy verbs and resource-types can change over time (and may differ for console vs API), use this approach:\n&#8211; If you are a tenancy admin, you can proceed in a lab.\n&#8211; If not, ask your admin for:\n  &#8211; Read access to Cloud Advisor recommendations for specific compartments\n  &#8211; Manage access to the specific services you will remediate<\/p>\n\n\n\n<p><strong>Verify the exact IAM policy statements in official docs<\/strong> for Cloud Advisor and any related API service name.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor itself is commonly treated as part of OCI governance features, but <strong>always verify pricing<\/strong>.<\/li>\n<li>The resources you create and the remediations you perform (e.g., block volumes, compute shapes, load balancers) can incur charges.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools (optional but helpful)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console (required for this tutorial)<\/li>\n<li>OCI Cloud Shell (optional, convenient)<\/li>\n<li>OCI CLI\/SDK (optional; only if you automate\u2014verify current support for Cloud Advisor\/Optimizer)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor is accessed via the console; recommendation coverage may vary by region and service.<\/li>\n<li>Choose a region where you are already deploying resources.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standard OCI service limits apply to the resources you create (compute instances, volumes, etc.).<\/li>\n<li>Recommendation generation may have internal service constraints; verify if you see delays.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services<\/h3>\n\n\n\n<p>None strictly required to <em>view<\/em> Cloud Advisor, but you will need real OCI resources deployed to get meaningful recommendations.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing model (how costs work)<\/h3>\n\n\n\n<p>Cloud Advisor is an advisory\/governance capability. In many cloud providers, \u201cadvisor\u201d features are included at no additional charge; however, <strong>you must confirm OCI\u2019s current pricing position<\/strong> for Cloud Advisor in the official pricing documentation.<\/p>\n\n\n\n<p>Use these official starting points:\n&#8211; Oracle Cloud pricing: https:\/\/www.oracle.com\/cloud\/pricing\/\n&#8211; OCI price list: https:\/\/www.oracle.com\/cloud\/price-list\/\n&#8211; Oracle Cloud cost estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/p>\n\n\n\n<p>If Cloud Advisor is included at no additional charge (common pattern), your costs are typically <strong>indirect<\/strong>, coming from:\n&#8211; The OCI resources you operate (Compute, Storage, Load Balancer, Database, etc.)\n&#8211; Logging, monitoring, and analytics services you choose to enable for validation and operations\n&#8211; Data egress\/networking charges when exporting data out of OCI (depending on your network path and region)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions to understand (even if Cloud Advisor is \u201cfree\u201d)<\/h3>\n\n\n\n<p>Even when the advisor feature is not metered, its recommendations often drive changes that affect billing:\n&#8211; <strong>Compute shape\/size changes<\/strong> alter hourly compute cost.\n&#8211; <strong>Storage deletion<\/strong> reduces GB-month charges.\n&#8211; <strong>Network architecture changes<\/strong> (NAT gateways, load balancers, public IPs) can change monthly\/hourly and data processing fees.\n&#8211; <strong>High availability improvements<\/strong> often increase cost (more instances, multi-AD\/region patterns).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud Free Tier varies by region and program terms.  <\/li>\n<li>Some Always Free resources may be sufficient for a lab, but recommendations might require time\/usage telemetry.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Main cost drivers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keeping \u201ctest\u201d resources running unintentionally (common)<\/li>\n<li>Orphaned block volumes \/ boot volumes<\/li>\n<li>Load balancers or gateways left behind after migrations<\/li>\n<li>Oversized compute\/database shapes<\/li>\n<li>Multi-region HA expansions (intentional but cost-increasing)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden\/indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Operational overhead<\/strong>: engineering time to review and remediate.<\/li>\n<li><strong>Change risk<\/strong>: rightsizing can affect performance if done without validation.<\/li>\n<li><strong>Observability<\/strong>: additional logs\/metrics retention can add cost.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Viewing Cloud Advisor in-console does not typically create data transfer charges.<\/li>\n<li>Exporting reports out of OCI or integrating with external tools may involve egress charges depending on your setup.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost with Cloud Advisor (practical tactics)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implement a recurring review:<\/li>\n<li>Weekly for non-prod<\/li>\n<li>Monthly for prod (or aligned to release cycles)<\/li>\n<li>Prioritize:<\/li>\n<li>\u201cNo-risk deletions\u201d (truly unused resources)<\/li>\n<li>\u201cLow-risk changes\u201d (storage tier adjustments, schedule automation)<\/li>\n<li>\u201cHigher-risk rightsizing\u201d (requires performance validation)<\/li>\n<li>Use tagging and compartments to assign owners and prevent resource sprawl.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (no fabricated numbers)<\/h3>\n\n\n\n<p>A low-cost starter approach:\n&#8211; Use an Always Free or minimal environment.\n&#8211; Review Cloud Advisor weekly.\n&#8211; Delete orphaned resources promptly.\nBecause OCI pricing is region- and SKU-dependent, <strong>use the cost estimator<\/strong> and your region\u2019s price list to calculate:\n&#8211; 1 small VM instance (if used)\n&#8211; 1 small block volume (if used)\n&#8211; Any networking components (if created)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>In production, Cloud Advisor often leads to:\n&#8211; Net savings from removing waste (idle compute, unused storage)\n&#8211; Potential cost increases when implementing best practices (HA, backups)\nA mature approach tracks both:\n&#8211; <strong>Savings realized<\/strong> (validated in Cost Analysis)\n&#8211; <strong>Risk reduced<\/strong> (tracked through compliance\/security KPIs)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab focuses on a realistic governance workflow: you will <strong>access Cloud Advisor<\/strong>, scope it to a compartment, review recommendations, and prepare a remediation loop. Because recommendations can take time to generate (often hours to a day depending on the signal), the lab includes an approach that is executable immediately and a \u201cwait-for-recommendation\u201d follow-up.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access <strong>Cloud Advisor<\/strong> in Oracle Cloud (OCI).<\/li>\n<li>Scope recommendations to a dedicated lab compartment.<\/li>\n<li>Review recommendation details and export\/share findings.<\/li>\n<li>(If available) remediate one low-risk recommendation safely.<\/li>\n<li>Validate that remediation is reflected operationally (and eventually in Cloud Advisor).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create a compartment dedicated to governance experiments.\n2. Create a deliberately \u201creview-worthy\u201d resource (optional) that may later generate a recommendation.\n3. Navigate Cloud Advisor, filter by compartment and category, and understand recommendation lifecycle.\n4. Export\/document recommendations for tracking.\n5. Remediate an item (if available) using safe change practices.\n6. Clean up all lab resources.<\/p>\n\n\n\n<blockquote>\n<p>Expected timing: 30\u201360 minutes for steps 1\u20134. Step 5 depends on whether you have recommendations available; some environments will require waiting for the recommendation generation cycle.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Create a dedicated compartment for the lab<\/h3>\n\n\n\n<p><strong>Why:<\/strong> Compartments are the core governance boundary in OCI. Cloud Advisor recommendations are easier to triage when you isolate lab resources.<\/p>\n\n\n\n<p><strong>Console steps<\/strong>\n1. Sign in to the <strong>OCI Console<\/strong>.\n2. Open the navigation menu and go to <strong>Identity &amp; Security<\/strong> \u2192 <strong>Compartments<\/strong>.\n3. Click <strong>Create Compartment<\/strong>.\n4. Name: <code>cloud-advisor-lab<\/code>\n5. Description: <code>Lab compartment for Cloud Advisor tutorial<\/code>\n6. Parent compartment: typically your root compartment (or a dedicated training parent).\n7. Click <strong>Create Compartment<\/strong>.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A compartment named <code>cloud-advisor-lab<\/code> exists and is Active.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; You can select the compartment in the compartment dropdown at the top of the console.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2 (Optional): Create a low-cost \u201ccandidate\u201d resource that may trigger a recommendation later<\/h3>\n\n\n\n<p>Because Cloud Advisor recommendations often rely on periodic analysis, you may not see new recommendations immediately. This optional step creates a \u201cresource hygiene\u201d candidate you can later evaluate.<\/p>\n\n\n\n<p><strong>Option A (common hygiene example): Create an unattached block volume<\/strong>\n1. Go to <strong>Storage<\/strong> \u2192 <strong>Block Storage<\/strong> \u2192 <strong>Block Volumes<\/strong>.\n2. Select compartment: <code>cloud-advisor-lab<\/code>.\n3. Click <strong>Create Block Volume<\/strong>.\n4. Use the smallest size permitted in your region and account.\n5. Do <strong>not<\/strong> attach it to an instance.\n6. Create it.<\/p>\n\n\n\n<p><strong>Cost note:<\/strong> Block volumes can incur GB-month charges. Delete it during cleanup.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; An unattached block volume exists in the lab compartment.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The block volume shows as Available (not attached).<\/p>\n\n\n\n<p><strong>Option B: Skip resource creation<\/strong>\n&#8211; If you already have workloads in your tenancy, you can proceed without creating anything. Cloud Advisor may already have recommendations.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Open Cloud Advisor and scope to your lab compartment<\/h3>\n\n\n\n<p><strong>Console steps<\/strong>\n1. Open the navigation menu.\n2. Go to <strong>Governance &amp; Administration<\/strong> \u2192 <strong>Cloud Advisor<\/strong>.<br\/>\n   &#8211; If you don\u2019t see it, use the console search bar for \u201cCloud Advisor\u201d.<\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>In Cloud Advisor, set:\n   &#8211; <strong>Compartment<\/strong>: <code>cloud-advisor-lab<\/code> (and optionally include child compartments if your UI supports it).\n   &#8211; <strong>Category\/Pillar filter<\/strong>: start with \u201cAll\u201d to see everything.\n   &#8211; <strong>Status filter<\/strong>: \u201cActive\u201d (or equivalent).<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Cloud Advisor loads and shows either:\n  &#8211; A list of recommendations, or\n  &#8211; An empty state like \u201cNo recommendations found\u201d for that scope.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Change the compartment filter between root and <code>cloud-advisor-lab<\/code> and confirm the recommendation list changes (or remains empty if none exist).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Review recommendation details and capture evidence<\/h3>\n\n\n\n<p>If you see recommendations:\n1. Click one recommendation.\n2. Record:\n   &#8211; Recommendation title\n   &#8211; Impacted resource OCID\/name\n   &#8211; Suggested action\n   &#8211; Any estimated savings\/impact\n   &#8211; Any linked documentation (if present)<\/p>\n\n\n\n<p>If you do <strong>not<\/strong> see recommendations:\n&#8211; Record the empty state and confirm:\n  &#8211; You are in the correct <strong>region<\/strong>\n  &#8211; You scoped to the intended <strong>compartment<\/strong>\n  &#8211; You have sufficient IAM permissions<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a documented snapshot of current recommendations (or confirmed none are available yet).<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Navigate back to the list and apply filters (category\/status) to confirm the UI behavior.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Export recommendations for tracking (or create a simple tracking log)<\/h3>\n\n\n\n<p>Different OCI services offer export in different ways, and Cloud Advisor export capability may vary by UI version. Use one of these approaches:<\/p>\n\n\n\n<p><strong>Approach A: Use built-in export (if available)<\/strong>\n&#8211; Look for an <strong>Export<\/strong> action (CSV or similar).\n&#8211; Export recommendations for the scoped compartment.\n&#8211; Store the export in your team\u2019s documentation system.<\/p>\n\n\n\n<p><strong>Approach B: Manual tracking (always works)<\/strong>\nCreate a simple table in your notes with:\n&#8211; Date\n&#8211; Compartment\n&#8211; Recommendation\n&#8211; Resource\n&#8211; Owner\n&#8211; Decision (Remediate \/ Accept risk \/ Need analysis)\n&#8211; Target date<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a repeatable artifact that supports governance workflows (FinOps\/SRE\/security).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Remediate one low-risk recommendation (if available)<\/h3>\n\n\n\n<p>This step depends on your tenancy having at least one recommendation and on you having permission to change the underlying resource.<\/p>\n\n\n\n<p><strong>Safe remediation candidates<\/strong>\n&#8211; Delete truly unused resources (confirm no dependencies).\n&#8211; Remove orphaned storage (after confirming data is not needed).\n&#8211; Release unused public IPs (after confirming no DNS or dependencies).<\/p>\n\n\n\n<p><strong>Example remediation (if you have an orphaned\/unattached volume recommendation)<\/strong>\n1. Go to <strong>Storage<\/strong> \u2192 <strong>Block Storage<\/strong> \u2192 <strong>Block Volumes<\/strong>.\n2. Select the impacted volume.\n3. Confirm it is not attached and not needed.\n4. Click <strong>Terminate<\/strong> (delete).\n5. Confirm deletion.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The unused resource is removed.\n&#8211; Your costs should decrease (validated later in Cost Analysis).\n&#8211; Cloud Advisor may take time to refresh and clear\/close the recommendation.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The resource no longer exists in the compartment.\n&#8211; OCI Audit contains an event for the deletion action (Identity &amp; Security \u2192 Audit).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use the following checklist:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Cloud Advisor access<\/strong>\n   &#8211; You can open Governance &amp; Administration \u2192 Cloud Advisor.<\/p>\n<\/li>\n<li>\n<p><strong>Correct scoping<\/strong>\n   &#8211; Filtering by compartment works.\n   &#8211; You can see either recommendations or a confirmed empty state.<\/p>\n<\/li>\n<li>\n<p><strong>Action verification (if remediated)<\/strong>\n   &#8211; The resource change is visible in the relevant service page.\n   &#8211; OCI Audit shows the change event.\n   &#8211; (Later) Cost Analysis shows reduced spend trend (timing depends on billing data update cycle).\n   &#8211; (Later) Cloud Advisor refresh removes or updates the recommendation.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p><strong>Issue: \u201cCloud Advisor not visible in the console\u201d<\/strong>\n&#8211; Confirm your account is in OCI (not a different Oracle Cloud portal).\n&#8211; Use console search for \u201cCloud Advisor\u201d.\n&#8211; Verify your user is in the correct tenancy.<\/p>\n\n\n\n<p><strong>Issue: Permission\/authorization errors<\/strong>\n&#8211; You likely need additional IAM policies to read recommendations or view compartments.\n&#8211; If you are not a tenancy admin, request:\n  &#8211; Read access to Cloud Advisor recommendations\n  &#8211; Inspect permissions for target services\n  &#8211; Manage permissions to implement remediations<br\/>\n&#8211; <strong>Verify exact policy syntax in official docs<\/strong> because resource-type names can differ between UI and API surfaces.<\/p>\n\n\n\n<p><strong>Issue: No recommendations appear<\/strong>\n&#8211; This can be normal for:\n  &#8211; New tenancies\n  &#8211; New compartments with minimal resources\n  &#8211; Recently created resources without enough telemetry\n&#8211; Wait for the next recommendation refresh cycle (often daily).\n&#8211; Check another compartment that has active resources to confirm the UI works.<\/p>\n\n\n\n<p><strong>Issue: Recommendation seems wrong<\/strong>\n&#8211; Validate the underlying metrics and configuration.\n&#8211; Check whether the resource has special workload constraints.\n&#8211; Treat Cloud Advisor as guidance, not as an authoritative truth source.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>Delete any lab resources you created:\n   &#8211; Unattached block volumes\n   &#8211; Instances, load balancers, gateways, etc.<\/p>\n<\/li>\n<li>\n<p>Delete the compartment (only if it contains no resources):\n   &#8211; Identity &amp; Security \u2192 Compartments\n   &#8211; Select <code>cloud-advisor-lab<\/code>\n   &#8211; Delete (OCI requires it to be empty)<\/p>\n<\/li>\n<li>\n<p>Confirm Cost Analysis stops showing the lab resource spend (billing data may lag).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use Cloud Advisor as part of a broader <strong>landing zone<\/strong> strategy:<\/li>\n<li>Compartments by environment and ownership<\/li>\n<li>Standard tagging for cost centers and application IDs<\/li>\n<li>Prefer patterns that reduce operational complexity:<\/li>\n<li>Fewer \u201cpet\u201d instances, more standardized deployment patterns<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Apply <strong>least privilege<\/strong>:<\/li>\n<li>Let app teams view recommendations for their compartments<\/li>\n<li>Restrict remediation permissions to change-controlled roles<\/li>\n<li>Separate duties:<\/li>\n<li>View-only roles (review)<\/li>\n<li>Operator roles (implement)<\/li>\n<li>Audit\/compliance roles (validate)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establish a cadence:<\/li>\n<li>Weekly in non-prod<\/li>\n<li>Monthly in prod<\/li>\n<li>Track outcomes:<\/li>\n<li>Estimated savings (Cloud Advisor) vs realized savings (Cost Analysis)<\/li>\n<li>Use tags to improve cost attribution:<\/li>\n<li><code>CostCenter<\/code>, <code>Application<\/code>, <code>Environment<\/code>, <code>Owner<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Don\u2019t blindly right-size:<\/li>\n<li>Validate with OCI Monitoring metrics<\/li>\n<li>Test during low-risk windows<\/li>\n<li>Use canaries:<\/li>\n<li>Apply changes to one node\/one compartment first<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat availability recommendations as <strong>design prompts<\/strong>:<\/li>\n<li>Verify RTO\/RPO requirements<\/li>\n<li>Confirm the workload\u2019s HA design is consistent with business impact<\/li>\n<li>Use multi-instance and failure-domain-aware patterns where required.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Turn recommendations into a managed backlog:<\/li>\n<li>Assign an owner<\/li>\n<li>Define a due date<\/li>\n<li>Track remediation status<\/li>\n<li>Document decision outcomes:<\/li>\n<li>Why it was remediated<\/li>\n<li>Why it was dismissed\/accepted<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use predictable naming to speed triage:<\/li>\n<li><code>app-env-region-component-##<\/code><\/li>\n<li>Enforce required tags (where your governance model supports it)<\/li>\n<li>Keep compartments aligned to ownership boundaries; don\u2019t mix unrelated projects.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor visibility is gated by <strong>OCI IAM<\/strong>.<\/li>\n<li>Recommendations can reveal resource metadata (names, types, compartment structure). Treat it as sensitive operational data.<\/li>\n<\/ul>\n\n\n\n<p><strong>Recommendations<\/strong>\n&#8211; Grant access based on least privilege.\n&#8211; Avoid broad tenancy-wide read access unless necessary for central governance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor consumes metadata and telemetry from OCI services; encryption at rest\/in transit for underlying services follows OCI\u2019s service design.  <\/li>\n<li>For sensitive exports (CSV, reports), store them in encrypted storage and restrict access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access is via OCI Console over HTTPS.<\/li>\n<li>Be careful when exporting recommendations to external systems; data may include resource identifiers.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Advisor should not require you to store secrets.<\/li>\n<li>If you automate via API:<\/li>\n<li>Prefer OCI user auth patterns supported by your organization (federation\/SSO)<\/li>\n<li>Avoid embedding API keys in code repositories<\/li>\n<li>Use secure secret storage solutions (verify OCI-native options you use)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Actual remediations are logged in <strong>OCI Audit<\/strong> because they modify resources.<\/li>\n<li>Use Audit to answer:<\/li>\n<li>Who changed what?<\/li>\n<li>When did it happen?<\/li>\n<li>In which compartment?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat Cloud Advisor as an input to compliance, not the compliance system itself.<\/li>\n<li>For regulated environments:<\/li>\n<li>Link remediation actions to change tickets.<\/li>\n<li>Maintain evidence: recommendation snapshot + change logs + validation metrics.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Over-granting permissions so everyone can \u201cmanage\u201d resources in response to recommendations.<\/li>\n<li>Dismissing security-related recommendations without documenting risk acceptance.<\/li>\n<li>Exporting recommendation data to uncontrolled endpoints.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralize governance in a small group, but allow decentralized execution:<\/li>\n<li>Central team reviews and prioritizes<\/li>\n<li>App teams implement within their compartments under controls<\/li>\n<li>Use compartment boundaries and tagging to enforce policy at scale.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because OCI evolves, verify specifics in official docs. Common limitations\/gotchas include:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Recommendation latency<\/strong>\n   &#8211; Recommendations may not be real-time; some require days of telemetry.<\/p>\n<\/li>\n<li>\n<p><strong>Coverage gaps<\/strong>\n   &#8211; Not all OCI services\/resources produce recommendations.<\/p>\n<\/li>\n<li>\n<p><strong>False positives \/ context blindness<\/strong>\n   &#8211; A resource that looks idle may be intentionally provisioned for failover, batch windows, or compliance.<\/p>\n<\/li>\n<li>\n<p><strong>Permissions mismatch<\/strong>\n   &#8211; Users may see recommendations but lack permission to remediate.<\/p>\n<\/li>\n<li>\n<p><strong>Change risk<\/strong>\n   &#8211; Rightsizing can degrade performance if done without testing.<\/p>\n<\/li>\n<li>\n<p><strong>Cost estimates are estimates<\/strong>\n   &#8211; Always validate with Cost Analysis and billing reports.<\/p>\n<\/li>\n<li>\n<p><strong>Multi-region complexity<\/strong>\n   &#8211; Recommendations may be region-specific; ensure you are looking at the correct region.<\/p>\n<\/li>\n<li>\n<p><strong>Compartment hierarchy confusion<\/strong>\n   &#8211; Recommendations can be missed if you scope to the wrong compartment or don\u2019t include children.<\/p>\n<\/li>\n<li>\n<p><strong>Operational workflow gaps<\/strong>\n   &#8211; Without a process (owners, cadence), recommendations become noise.<\/p>\n<\/li>\n<li>\n<p><strong>Export\/automation variability<\/strong>\n   &#8211; UI export and API surfaces can change; confirm supported integrations and endpoints.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Cloud Advisor is conceptually similar to \u201cadvisor\u201d services in other clouds, but OCI-specific in implementation and IAM\/compartment integration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Nearest services in Oracle Cloud<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cloud Guard<\/strong>: security posture management and threat detection\/response workflows (security-focused).<\/li>\n<li><strong>Cost Analysis \/ Cost Management<\/strong>: financial reporting, budgets, and cost attribution.<\/li>\n<li><strong>Monitoring + Alarms<\/strong>: real-time telemetry and alerting, not recommendations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Nearest services in other clouds<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AWS Trusted Advisor<\/strong>: best-practice checks across cost, performance, security, fault tolerance, service limits.<\/li>\n<li><strong>Azure Advisor<\/strong>: recommendations for cost, reliability, operational excellence, performance, security.<\/li>\n<li><strong>Google Cloud Recommender<\/strong>: recommendations across IAM, cost, performance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Open-source \/ self-managed alternatives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Policy-as-code and scanning tools (coverage varies):<\/li>\n<li>Cloud Custodian<\/li>\n<li>Open Policy Agent (OPA) + custom rules<\/li>\n<li>Custom scripts using SDKs + internal governance logic<br\/>\nThese can be powerful but require engineering effort and ongoing maintenance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Oracle Cloud \u2013 Cloud Advisor<\/strong><\/td>\n<td>OCI tenants needing centralized recommendations<\/td>\n<td>Native to OCI; compartment-aware governance; low operational overhead<\/td>\n<td>Coverage and refresh cycles vary; some contexts require manual validation<\/td>\n<td>You want OCI-native recommendations and an operational review loop<\/td>\n<\/tr>\n<tr>\n<td><strong>Oracle Cloud \u2013 Cloud Guard<\/strong><\/td>\n<td>Security posture + threat detection<\/td>\n<td>Security-focused; policies\/detectors\/responder workflows (verify features in Cloud Guard docs)<\/td>\n<td>Not primarily cost\/performance optimization<\/td>\n<td>You need security controls and continuous security monitoring<\/td>\n<\/tr>\n<tr>\n<td><strong>Oracle Cloud \u2013 Cost Analysis<\/strong><\/td>\n<td>FinOps reporting and spend investigation<\/td>\n<td>Precise billing-aligned reporting<\/td>\n<td>Not prescriptive; doesn\u2019t tell you what to fix<\/td>\n<td>You need authoritative cost reporting and budgets<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Trusted Advisor<\/strong><\/td>\n<td>AWS-centric optimization<\/td>\n<td>Broad checks; strong ecosystem<\/td>\n<td>AWS-only<\/td>\n<td>Your workloads are primarily on AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Advisor<\/strong><\/td>\n<td>Azure-centric optimization<\/td>\n<td>Integrated Azure recommendations<\/td>\n<td>Azure-only<\/td>\n<td>Your workloads are primarily on Azure<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Recommender<\/strong><\/td>\n<td>GCP-centric optimization<\/td>\n<td>Strong recommender framework<\/td>\n<td>GCP-only<\/td>\n<td>Your workloads are primarily on GCP<\/td>\n<\/tr>\n<tr>\n<td><strong>Cloud Custodian \/ custom governance<\/strong><\/td>\n<td>Highly customized controls<\/td>\n<td>Custom rules and enforcement<\/td>\n<td>Build\/maintain cost; requires engineering<\/td>\n<td>You need bespoke compliance and automation beyond native advisors<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: multi-compartment optimization program<\/h3>\n\n\n\n<p><strong>Problem<\/strong><br\/>\nA large enterprise runs hundreds of OCI compartments across many business units. Costs creep upward due to orphaned storage and over-provisioned non-prod systems, while security teams struggle to keep consistent hygiene across teams.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; OCI landing zone with:\n  &#8211; Compartments by BU\/environment\n  &#8211; Standard tags: <code>CostCenter<\/code>, <code>Owner<\/code>, <code>AppID<\/code>, <code>Environment<\/code>\n&#8211; Cloud Advisor used as the central recommendation inventory\n&#8211; A monthly governance cycle:\n  &#8211; Central platform team exports recommendations and routes them to owners\n  &#8211; App teams remediate within change windows\n&#8211; Validation:\n  &#8211; OCI Audit for evidence of changes\n  &#8211; OCI Monitoring for performance validation\n  &#8211; OCI Cost Analysis for realized savings reporting<\/p>\n\n\n\n<p><strong>Why Cloud Advisor was chosen<\/strong>\n&#8211; Native to OCI, compartment-scoped, and aligns with how OCI environments are governed.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Reduced waste (storage and idle resources)\n&#8211; Faster triage and ownership mapping\n&#8211; Better auditability of \u201cwhy changes were made\u201d (recommendations + Audit logs)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: lightweight FinOps loop<\/h3>\n\n\n\n<p><strong>Problem<\/strong><br\/>\nA startup runs a small OCI footprint but frequently spins up dev\/test resources. Costs fluctuate and engineers forget to tear down resources after experiments.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; One compartment for <code>prod<\/code>, one for <code>dev<\/code>\n&#8211; Weekly Cloud Advisor review (15 minutes)\n&#8211; Simple playbook:\n  &#8211; Delete orphaned volumes\n  &#8211; Shut down unused instances\n  &#8211; Track decisions in a shared doc<\/p>\n\n\n\n<p><strong>Why Cloud Advisor was chosen<\/strong>\n&#8211; Minimal setup, low overhead, easy for a small team.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Fewer surprises on monthly bill\n&#8211; Cleaner environments and fewer abandoned resources\n&#8211; A habit of continuous optimization without heavy tooling<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is Cloud Advisor the same as Cloud Guard?<\/strong><br\/>\nNo. Cloud Advisor focuses on recommendations across operational pillars (cost\/performance\/availability\/security where supported). Cloud Guard is primarily a security posture and threat-focused service. They complement each other.<\/p>\n\n\n\n<p>2) <strong>Do I need agents on my instances for Cloud Advisor?<\/strong><br\/>\nTypically no. Cloud Advisor usually relies on OCI control plane data and service telemetry. Verify per recommendation type.<\/p>\n\n\n\n<p>3) <strong>Why do I see no recommendations?<\/strong><br\/>\nCommon reasons: new tenancy, no supported resources, insufficient telemetry history, wrong region, wrong compartment scope, or missing permissions.<\/p>\n\n\n\n<p>4) <strong>How often are recommendations updated?<\/strong><br\/>\nIt depends on the recommendation type and OCI\u2019s refresh cycles. Some may be daily or periodic rather than real-time. Verify in official docs.<\/p>\n\n\n\n<p>5) <strong>Can Cloud Advisor automatically fix issues?<\/strong><br\/>\nCloud Advisor primarily recommends; remediation is generally performed by you in the underlying OCI services. Some recommendations may provide streamlined actions\u2014verify current capabilities.<\/p>\n\n\n\n<p>6) <strong>Are Cloud Advisor cost savings guaranteed?<\/strong><br\/>\nNo. Any savings are estimates and depend on actual usage and billing. Validate with Cost Analysis.<\/p>\n\n\n\n<p>7) <strong>Does dismissing a recommendation remove risk?<\/strong><br\/>\nNo. It only changes workflow state. Document why it was dismissed (accepted risk, false positive, or not applicable).<\/p>\n\n\n\n<p>8) <strong>Can I use Cloud Advisor in a multi-region setup?<\/strong><br\/>\nYes, but recommendations may be region-specific. Ensure you review the correct region(s).<\/p>\n\n\n\n<p>9) <strong>How do I assign recommendations to teams?<\/strong><br\/>\nUse compartment ownership + tags. Export recommendations and route them based on tag\/compartment mapping.<\/p>\n\n\n\n<p>10) <strong>What\u2019s the best cadence for reviews?<\/strong><br\/>\nWeekly for non-prod and monthly for prod is common. High-change organizations may review more frequently.<\/p>\n\n\n\n<p>11) <strong>Can I integrate recommendations into Jira\/ServiceNow?<\/strong><br\/>\nOften yes via export or API, but the exact API naming and endpoints must be verified in current OCI docs.<\/p>\n\n\n\n<p>12) <strong>Does Cloud Advisor replace Monitoring alarms?<\/strong><br\/>\nNo. Monitoring alarms are for near-real-time detection; Cloud Advisor is for periodic optimization recommendations.<\/p>\n\n\n\n<p>13) <strong>What permissions do developers need to use Cloud Advisor?<\/strong><br\/>\nAt minimum, read access to recommendations for their compartments. To remediate, they also need manage permissions for the target resources. Verify exact IAM policy resource types in docs.<\/p>\n\n\n\n<p>14) <strong>Is Cloud Advisor suitable for regulated environments?<\/strong><br\/>\nYes as a governance input, but you must maintain change records, approvals, and evidence via Audit and ITSM.<\/p>\n\n\n\n<p>15) <strong>How do I prove value from Cloud Advisor?<\/strong><br\/>\nTrack: number of recommendations remediated, realized cost savings (Cost Analysis), and risk reduction metrics (security posture improvements, fewer incidents).<\/p>\n\n\n\n<p>16) <strong>What should I do if a recommendation conflicts with application requirements?<\/strong><br\/>\nTreat it as guidance. Validate constraints with application owners and SREs, and document risk acceptance if you choose not to implement it.<\/p>\n\n\n\n<p>17) <strong>Can Cloud Advisor help with tagging strategy?<\/strong><br\/>\nIt can benefit from good tagging because ownership routing improves. Tagging recommendations themselves may not be a feature; use governance processes and exports.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Cloud Advisor<\/h2>\n\n\n\n<p>Because Oracle documentation URLs can evolve, if a link changes, start from the OCI documentation home and search for \u201cCloud Advisor\u201d.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Documentation home: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/home.htm<\/td>\n<td>Starting point to search for the latest Cloud Advisor docs<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Cloud Advisor (OCI docs): https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/CloudAdvisor\/home.htm<\/td>\n<td>Primary documentation hub for Cloud Advisor (verify current URL if it changes)<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Pricing: https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<td>Authoritative pricing entry point for OCI services<\/td>\n<\/tr>\n<tr>\n<td>Official price list<\/td>\n<td>Oracle Cloud Price List: https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<td>SKU-level pricing reference; validate whether Cloud Advisor is billed separately<\/td>\n<\/tr>\n<tr>\n<td>Official cost calculator<\/td>\n<td>Oracle Cloud Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Build region-specific estimates for resources impacted by recommendations<\/td>\n<\/tr>\n<tr>\n<td>Official architecture center<\/td>\n<td>Oracle Architecture Center: https:\/\/docs.oracle.com\/en\/solutions\/<\/td>\n<td>Reference architectures and best practices that often align with recommendation themes<\/td>\n<\/tr>\n<tr>\n<td>Official governance docs<\/td>\n<td>OCI IAM overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/overview.htm<\/td>\n<td>Required to correctly scope access to recommendations and remediation actions<\/td>\n<\/tr>\n<tr>\n<td>Official governance docs<\/td>\n<td>OCI Compartments overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Tasks\/managingcompartments.htm<\/td>\n<td>Helps you structure recommendation ownership and review workflows<\/td>\n<\/tr>\n<tr>\n<td>Official operations docs<\/td>\n<td>OCI Audit overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Audit\/Concepts\/auditoverview.htm<\/td>\n<td>Essential for tracking remediation actions and compliance evidence<\/td>\n<\/tr>\n<tr>\n<td>Official operations docs<\/td>\n<td>OCI Monitoring overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Monitoring\/Concepts\/monitoringoverview.htm<\/td>\n<td>Validates performance after implementing rightsizing recommendations<\/td>\n<\/tr>\n<tr>\n<td>Video platform<\/td>\n<td>Oracle Cloud YouTube channel: https:\/\/www.youtube.com\/@OracleCloudInfrastructure<\/td>\n<td>Look for Cloud Advisor\/Optimizer, governance, and FinOps-related videos (search within channel)<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Oracle Cloud Free Tier documentation (entry point): https:\/\/www.oracle.com\/cloud\/free\/<\/td>\n<td>Useful for building low-cost labs that can later generate recommendations<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>The following are third-party training providers to explore. Availability, course accuracy, and instructor quality can vary\u2014review each site directly.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>DevOpsSchool.com<\/strong>\n   &#8211; <strong>Suitable audience:<\/strong> DevOps engineers, SREs, cloud engineers, platform teams\n   &#8211; <strong>Likely learning focus:<\/strong> OCI operations, governance, DevOps practices, cloud tooling\n   &#8211; <strong>Mode:<\/strong> check website\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>ScmGalaxy.com<\/strong>\n   &#8211; <strong>Suitable audience:<\/strong> Beginners to intermediate DevOps learners, SCM-focused teams\n   &#8211; <strong>Likely learning focus:<\/strong> DevOps fundamentals, CI\/CD, configuration management, cloud basics\n   &#8211; <strong>Mode:<\/strong> check website\n   &#8211; <strong>Website:<\/strong> https:\/\/www.scmgalaxy.com\/<\/p>\n<\/li>\n<li>\n<p><strong>CLoudOpsNow.in<\/strong>\n   &#8211; <strong>Suitable audience:<\/strong> Cloud operations practitioners, support\/ops engineers\n   &#8211; <strong>Likely learning focus:<\/strong> Cloud operations, monitoring, governance practices\n   &#8211; <strong>Mode:<\/strong> check website\n   &#8211; <strong>Website:<\/strong> https:\/\/cloudopsnow.in\/<\/p>\n<\/li>\n<li>\n<p><strong>SreSchool.com<\/strong>\n   &#8211; <strong>Suitable audience:<\/strong> SREs, reliability engineers, platform engineers\n   &#8211; <strong>Likely learning focus:<\/strong> SRE practices, incident management, reliability, observability\n   &#8211; <strong>Mode:<\/strong> check website\n   &#8211; <strong>Website:<\/strong> https:\/\/www.sreschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>AiOpsSchool.com<\/strong>\n   &#8211; <strong>Suitable audience:<\/strong> Operations and platform teams exploring AIOps\n   &#8211; <strong>Likely learning focus:<\/strong> AIOps concepts, operational analytics, automation\n   &#8211; <strong>Mode:<\/strong> check website\n   &#8211; <strong>Website:<\/strong> https:\/\/www.aiopsschool.com\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>These sites are listed as potential trainer platforms\/resources. Verify course listings, credentials, and relevance to Oracle Cloud Cloud Advisor before purchasing.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>RajeshKumar.xyz<\/strong>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps\/cloud training (verify current offerings)\n   &#8211; <strong>Suitable audience:<\/strong> DevOps and cloud learners\n   &#8211; <strong>Website:<\/strong> https:\/\/rajeshkumar.xyz\/<\/p>\n<\/li>\n<li>\n<p><strong>devopstrainer.in<\/strong>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps tools and practices (verify OCI-specific coverage)\n   &#8211; <strong>Suitable audience:<\/strong> Engineers learning DevOps\/toolchains\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopstrainer.in\/<\/p>\n<\/li>\n<li>\n<p><strong>devopsfreelancer.com<\/strong>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps freelancing services and\/or training resources (verify)\n   &#8211; <strong>Suitable audience:<\/strong> Teams seeking hands-on assistance or learning resources\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopsfreelancer.com\/<\/p>\n<\/li>\n<li>\n<p><strong>devopssupport.in<\/strong>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps support and training (verify)\n   &#8211; <strong>Suitable audience:<\/strong> Ops\/DevOps teams needing support-oriented learning\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopssupport.in\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>The following sites are listed as potential consulting providers. Validate service scope, references, and OCI expertise directly with each organization.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>cotocus.com<\/strong>\n   &#8211; <strong>Likely service area:<\/strong> Cloud\/DevOps consulting (verify OCI specialization)\n   &#8211; <strong>Where they may help:<\/strong> Governance processes, cloud operations, optimization initiatives\n   &#8211; <strong>Consulting use case examples:<\/strong> FinOps review loop design, compartment\/tag strategy, operational playbooks\n   &#8211; <strong>Website:<\/strong> https:\/\/cotocus.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DevOpsSchool.com<\/strong>\n   &#8211; <strong>Likely service area:<\/strong> DevOps and cloud consulting\/training services\n   &#8211; <strong>Where they may help:<\/strong> Platform enablement, DevOps transformations, operations maturity\n   &#8211; <strong>Consulting use case examples:<\/strong> CI\/CD enablement aligned with governance, SRE operational processes, cloud cost optimization program support\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DEVOPSCONSULTING.IN<\/strong>\n   &#8211; <strong>Likely service area:<\/strong> DevOps consulting services (verify OCI-specific offerings)\n   &#8211; <strong>Where they may help:<\/strong> DevOps implementation, operational improvements, governance workflows\n   &#8211; <strong>Consulting use case examples:<\/strong> Recommendation triage workflow integration, audit-ready remediation process design\n   &#8211; <strong>Website:<\/strong> https:\/\/devopsconsulting.in\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Cloud Advisor (foundations)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>OCI fundamentals<\/strong>\n   &#8211; Regions, availability domains, fault domains\n   &#8211; Core services: Compute, Networking (VCN), Storage<\/li>\n<li><strong>Governance basics<\/strong>\n   &#8211; Tenancy, compartments, IAM policies, groups\n   &#8211; Tagging strategy and naming conventions<\/li>\n<li><strong>Operations basics<\/strong>\n   &#8211; OCI Monitoring, alarms, notifications\n   &#8211; OCI Audit and log review<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Cloud Advisor (to level up)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>FinOps on OCI<\/strong><\/li>\n<li>Cost Analysis, budgets (if used), showback\/chargeback models<\/li>\n<li><strong>Security posture<\/strong><\/li>\n<li>Cloud Guard, Security Zones (if applicable), SIEM integrations<\/li>\n<li><strong>Automation<\/strong><\/li>\n<li>Infrastructure as Code (Resource Manager\/Terraform)<\/li>\n<li>Scripting with OCI SDK\/CLI (verify Cloud Advisor\/Optimizer API support)<\/li>\n<li><strong>Reliability engineering<\/strong><\/li>\n<li>HA\/DR design patterns, runbooks, incident response<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use Cloud Advisor<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Cloud Operations Engineer<\/li>\n<li>DevOps Engineer \/ Platform Engineer<\/li>\n<li>Site Reliability Engineer (SRE)<\/li>\n<li>Cloud Security Engineer (as an input to posture review)<\/li>\n<li>FinOps Analyst \/ Cloud Cost Manager<\/li>\n<li>Solution Architect \/ Cloud Architect<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle certifications change over time. A common path is:\n&#8211; OCI foundations (entry-level)\n&#8211; OCI Architect Associate \u2192 OCI Architect Professional<br\/>\nVerify the latest Oracle certification catalog and whether any modules mention Cloud Advisor\/Optimizer explicitly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Monthly optimization report<\/strong>\n   &#8211; Export recommendations, categorize them, and track remediation outcomes<\/li>\n<li><strong>Compartment ownership mapping<\/strong>\n   &#8211; Enforce tags and route recommendations automatically to owners<\/li>\n<li><strong>Rightsizing playbook<\/strong>\n   &#8211; Define a safe process: baseline metrics \u2192 change \u2192 validate \u2192 rollback plan<\/li>\n<li><strong>Audit-ready remediation<\/strong>\n   &#8211; Link recommendation snapshots to OCI Audit events and change tickets<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI (Oracle Cloud Infrastructure):<\/strong> Oracle Cloud\u2019s infrastructure platform for compute, storage, networking, and managed services.<\/li>\n<li><strong>Tenancy:<\/strong> The top-level container for your OCI account and resources.<\/li>\n<li><strong>Compartment:<\/strong> A logical container within a tenancy used for organizing and isolating resources and access policies.<\/li>\n<li><strong>IAM (Identity and Access Management):<\/strong> OCI system for authentication and authorization using users, groups, dynamic groups, and policies.<\/li>\n<li><strong>Recommendation:<\/strong> A suggested improvement generated by Cloud Advisor based on observed configuration\/telemetry.<\/li>\n<li><strong>Remediation:<\/strong> The act of implementing a recommendation by changing, resizing, deleting, or reconfiguring OCI resources.<\/li>\n<li><strong>Audit log:<\/strong> OCI service that records API calls and console actions for governance and compliance.<\/li>\n<li><strong>FinOps:<\/strong> A practice that combines finance, operations, and engineering to manage cloud cost effectively.<\/li>\n<li><strong>Rightsizing:<\/strong> Adjusting resource size (CPU\/memory\/storage throughput) to match workload needs.<\/li>\n<li><strong>Telemetry:<\/strong> Operational data such as metrics, logs, and configuration state used to analyze workloads.<\/li>\n<li><strong>OCID:<\/strong> Oracle Cloud Identifier, a unique ID for OCI resources.<\/li>\n<li><strong>Landing zone:<\/strong> A standardized OCI environment setup (compartments, IAM, networking, logging) to support secure and scalable deployments.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Oracle Cloud <strong>Cloud Advisor<\/strong> is a Governance and Administration service that provides <strong>recommendations<\/strong> to improve your OCI environment across common operational priorities like <strong>cost efficiency, security posture, performance, and availability<\/strong> (coverage varies\u2014verify in official docs). It fits best as part of a continuous governance loop: <strong>review \u2192 validate \u2192 remediate \u2192 measure outcomes<\/strong>.<\/p>\n\n\n\n<p>Cost-wise, the biggest financial impact usually comes not from Cloud Advisor itself but from the <strong>resources it helps you optimize<\/strong>\u2014unused storage, idle compute, and architecture changes. Security-wise, use <strong>least privilege IAM<\/strong>, rely on <strong>OCI Audit<\/strong> for evidence, and treat dismissals as documented risk acceptance rather than \u201cfixes.\u201d<\/p>\n\n\n\n<p>Use Cloud Advisor when you want practical, compartment-aligned guidance and a scalable way to keep OCI estates clean. Next, deepen your skills by pairing Cloud Advisor with <strong>OCI Cost Analysis<\/strong>, <strong>OCI Monitoring<\/strong>, and <strong>OCI Audit<\/strong>, and consider automation only after you\u2019ve validated the current Cloud Advisor\/Optimizer API surfaces in the official documentation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Governance and Administration<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[70,62],"tags":[],"class_list":["post-908","post","type-post","status-publish","format-standard","hentry","category-governance-and-administration","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=908"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/908\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}