{"id":915,"date":"2026-04-16T16:41:14","date_gmt":"2026-04-16T16:41:14","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-support-requests-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-governance-and-administration\/"},"modified":"2026-04-16T16:41:14","modified_gmt":"2026-04-16T16:41:14","slug":"oracle-cloud-support-requests-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-support-requests-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-governance-and-administration\/","title":{"rendered":"Oracle Cloud Support Requests 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>Support Requests<\/strong> is the built-in way to open, track, and collaborate on technical support cases for your Oracle Cloud tenancy. It is the operational \u201cbridge\u201d between your engineering teams and Oracle Support when something breaks, when you need guidance, or when you require formal changes such as service limit (quota) increases.<\/p>\n\n\n\n<p>In simple terms: <strong>Support Requests<\/strong> lets you create a ticket with Oracle, attach evidence (error messages, OCIDs, timestamps, logs), set severity, and receive responses\u2014without leaving the Oracle Cloud Console.<\/p>\n\n\n\n<p>Technically, Support Requests sits within Oracle Cloud\u2019s Governance and Administration experience and connects the OCI Console (and, for automation, OCI support\/incident management APIs where available) to Oracle\u2019s incident management systems. It uses Oracle Cloud Identity and Access Management (IAM) to determine who can create and manage requests, and it fits into your operational controls (auditability, least privilege, and standardized troubleshooting workflows).<\/p>\n\n\n\n<p>It solves a very real problem: when production systems are impacted or platform limits prevent deployments, teams need a secure, auditable, and structured way to engage the cloud provider\u2014fast\u2014while sharing the right diagnostic context.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Support Requests?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p><strong>Support Requests<\/strong> is Oracle Cloud\u2019s mechanism for interacting with Oracle Support for OCI-related issues and tasks: reporting incidents, requesting help, tracking progress, and documenting outcomes.<\/p>\n\n\n\n<blockquote>\n<p>Naming note: In Oracle Cloud documentation and UI, you may also see related terms such as <strong>Support<\/strong>, <strong>Support Center<\/strong>, <strong>Contact Support<\/strong>, or references to an incident\/case management API (often associated with Oracle\u2019s incident management services). The primary user-facing function in the console is commonly presented as <strong>Support Requests<\/strong>. If your tenancy UI uses different labels, verify in official docs for your account type and support plan.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities<\/h3>\n\n\n\n<p>Support Requests typically covers these capabilities (availability depends on support plan and tenancy permissions):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create a new support request with severity and product\/service context<\/li>\n<li>Track and update existing requests (add notes, respond to questions)<\/li>\n<li>Attach files (logs, screenshots, diagnostic exports) subject to size\/type limits<\/li>\n<li>View request history and Oracle responses<\/li>\n<li>Route requests to the right Oracle team via structured fields (service\/category\/problem type)<\/li>\n<li>Use it as the official record of provider engagement for incident review and compliance evidence<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Console Support Requests UI<\/strong>: primary interface for most teams<\/li>\n<li><strong>Identity and Access Management (IAM)<\/strong>: controls who can create\/view\/update requests<\/li>\n<li><strong>Oracle Support \/ Incident system<\/strong>: where the request is ultimately worked<\/li>\n<li><strong>Optional APIs\/SDKs<\/strong>: some organizations automate case creation or listing (verify current API availability and prerequisites in official docs)<\/li>\n<li><strong>Audit and operational tooling<\/strong>: your internal runbooks, ticketing system, log storage, and monitoring that feed evidence into the request<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Governance and Administration service capability (operational support\/incident management)<\/li>\n<li>Not a compute\/networking\/data-plane service; it is primarily <strong>control-plane workflow and collaboration<\/strong><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope: regional vs global<\/h3>\n\n\n\n<p>Support Requests is best understood as:\n&#8211; <strong>Tenancy\/account-scoped<\/strong>: requests are associated with your Oracle Cloud account\/tenancy and your support entitlement.\n&#8211; Operationally <strong>global<\/strong> in the sense that it is not tied to a single region\u2019s data plane, though the issue you report will usually be tied to a specific region\/service. Always include the impacted region(s) in the request.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Oracle Cloud ecosystem<\/h3>\n\n\n\n<p>Support Requests is one of the \u201clast-mile\u201d governance tools that complements:\n&#8211; <strong>IAM<\/strong> (who can do what)\n&#8211; <strong>Audit<\/strong> (who did what in the tenancy)\n&#8211; <strong>Monitoring\/Logging<\/strong> (what happened)\n&#8211; <strong>Limits\/Quotas<\/strong> (why a deployment may be blocked)\n&#8211; <strong>Resource Manager \/ DevOps \/ CI\/CD<\/strong> (how changes were applied)\n&#8211; <strong>Tagging and compartments<\/strong> (how resources are organized for operations)<\/p>\n\n\n\n<p>In practice, when an alert fires and your SRE runbook ends with \u201cengage Oracle Support,\u201d Support Requests is the official workflow to do so.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Support Requests?<\/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 downtime and business impact<\/strong> by engaging the provider quickly with a structured process.<\/li>\n<li><strong>Faster escalation<\/strong> for paid support plans, with severity-based response handling.<\/li>\n<li><strong>Auditability and accountability<\/strong>: decisions, timelines, and remediation steps are recorded.<\/li>\n<li><strong>Vendor-backed guidance<\/strong> for complex OCI service behavior, limits, and edge cases.<\/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><strong>Correct routing<\/strong>: selecting the right service\/category gets you to the right support engineers faster.<\/li>\n<li><strong>Context-rich troubleshooting<\/strong>: OCIDs, work request IDs, timestamps, and logs can be attached and referenced.<\/li>\n<li><strong>Change enablement<\/strong>: many operational blockers are not \u201cbugs\u201d but require provider-side action (for example, service limit increases or back-end checks).<\/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><strong>Standardizes incident engagement<\/strong> across teams and shifts.<\/li>\n<li><strong>Improves handoffs<\/strong>: a request thread is the single source of truth for provider communications.<\/li>\n<li><strong>Supports post-incident reviews<\/strong>: the support case becomes part of the evidence trail.<\/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><strong>Controlled access<\/strong> via IAM rather than ad-hoc email threads.<\/li>\n<li><strong>Better data handling<\/strong>: teams can apply internal policies on what can be shared (redaction, no secrets).<\/li>\n<li><strong>Compliance evidence<\/strong>: change approvals, incident timelines, and vendor communications can be retained.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<p>Support Requests isn\u2019t a scalability mechanism itself, but it enables:\n&#8211; <strong>Scaling beyond default service limits<\/strong> (where Oracle allows increases)\n&#8211; <strong>Performance investigations<\/strong> with vendor assistance (network, storage, database services)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Production incidents, degraded service, or suspected OCI platform issues<\/li>\n<li>Persistent deployment failures after internal troubleshooting<\/li>\n<li>Account\/tenancy issues (limits, access problems, service enablement)<\/li>\n<li>Requests that require Oracle action, confirmation, or formal guidance<\/li>\n<li>Situations where you need traceable, contractual support interaction<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When they should not choose it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Purely internal application bugs where OCI is not implicated<\/li>\n<li>General \u201chow do I code this?\u201d questions (use internal engineering channels first)<\/li>\n<li>Requests that would expose sensitive data you cannot safely share (until you can sanitize)<\/li>\n<li>If you are on a support plan with limited entitlements and the issue is non-urgent, consider official community channels first (verify what Oracle provides for your account type)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Support Requests used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Financial services (strict audit trails, incident management)<\/li>\n<li>Healthcare and life sciences (compliance-driven operations)<\/li>\n<li>Retail and e-commerce (availability and performance sensitivity)<\/li>\n<li>SaaS and technology (fast-moving DevOps workflows, scaling needs)<\/li>\n<li>Government\/regulated sectors (formal escalation paths and evidence)<\/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>SRE\/Operations teams (incident response and escalation)<\/li>\n<li>Platform engineering teams (shared services, landing zones, guardrails)<\/li>\n<li>DevOps teams (CI\/CD failures, resource provisioning issues)<\/li>\n<li>Security teams (access issues, security event triage, compliance evidence)<\/li>\n<li>Network and infrastructure teams (connectivity, routing, edge cases)<\/li>\n<li>FinOps teams (billing anomalies, unexpected spend investigations\u2014where support can clarify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads and architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multi-region production platforms (where severity and region are critical)<\/li>\n<li>Regulated workloads needing evidence and vendor engagement records<\/li>\n<li>High-performance architectures (networking\/storage tuning investigations)<\/li>\n<li>Large multi-compartment enterprises with standardized ops playbooks<\/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>During major releases and migrations<\/li>\n<li>While scaling capacity (limits, performance issues)<\/li>\n<li>During outages or partial degradation events<\/li>\n<li>During tenancy governance changes (IAM\/compartment re-org impact)<\/li>\n<li>For provider-side maintenance coordination questions (verify exact mechanisms in your support plan)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: primary driver\u2014severity, escalation, and high-quality evidence matter most.<\/li>\n<li><strong>Dev\/test<\/strong>: often used for limit increases, provisioning failures, and service behavior clarification, especially early in a landing zone rollout.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Support Requests is a good fit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Production outage suspected to be OCI-related<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Your service is down; internal logs show upstream timeouts and OCI service errors.<\/li>\n<li><strong>Why it fits:<\/strong> Provides a severity-based escalation path and structured evidence sharing.<\/li>\n<li><strong>Example:<\/strong> Multiple compute instances in one region become unreachable; you open a Severity 1\/2 support request with instance OCIDs, VNIC details, and timestamps.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Service limit (quota) increase request<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Terraform\/Resource Manager fails with a \u201climit exceeded\u201d error.<\/li>\n<li><strong>Why it fits:<\/strong> Many limit increases require a formal support process.<\/li>\n<li><strong>Example:<\/strong> You need more block volumes or public IPs for a new environment; you submit a support request with desired limit values and business justification.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Intermittent network performance degradation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Latency spikes between subnets or to on-prem via FastConnect\/VPN.<\/li>\n<li><strong>Why it fits:<\/strong> Oracle Support can help interpret service behavior and advise on diagnostics.<\/li>\n<li><strong>Example:<\/strong> You attach MTR\/trace results, VCN\/DRG OCIDs, and Monitoring graphs showing the pattern.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Billing or metering investigation (FinOps support)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Spend increased unexpectedly; you need clarification on which SKU or usage dimension drove it.<\/li>\n<li><strong>Why it fits:<\/strong> Support can assist in interpreting billing artifacts and identifying misconfiguration patterns.<\/li>\n<li><strong>Example:<\/strong> After enabling a service feature, daily cost changes; you open a request with the cost report extracts and impacted compartments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) OCI Console\/Identity access issue<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Admin users cannot perform actions; permission errors persist.<\/li>\n<li><strong>Why it fits:<\/strong> Support can confirm platform-side issues and help validate IAM behavior.<\/li>\n<li><strong>Example:<\/strong> Policies appear correct but some API calls fail; you share exact error messages and request IDs (no secrets).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Region-specific service availability questions<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> You can\u2019t enable a service or feature in a target region.<\/li>\n<li><strong>Why it fits:<\/strong> Support can confirm service rollout status and any tenancy restrictions.<\/li>\n<li><strong>Example:<\/strong> You need a specific database feature in Region A; support clarifies availability and alternatives.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Resource provisioning stuck \/ work request failing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A work request stays in \u201cIn Progress\u201d or fails with an opaque error.<\/li>\n<li><strong>Why it fits:<\/strong> Oracle Support can inspect backend traces tied to work request IDs.<\/li>\n<li><strong>Example:<\/strong> A load balancer update fails repeatedly; you include the work request OCID and timestamps.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Security incident triage involving cloud account controls<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Suspicious activity detected; you need help confirming OCI-side events.<\/li>\n<li><strong>Why it fits:<\/strong> Support plus your internal security team can coordinate on evidence and platform telemetry.<\/li>\n<li><strong>Example:<\/strong> Unexpected IAM changes; you include Audit event IDs and request guidance on containment steps.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Managed service behavior clarification (e.g., DB, Kubernetes, integrations)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A managed service behaves differently than expected; docs are ambiguous for your scenario.<\/li>\n<li><strong>Why it fits:<\/strong> Support can provide authoritative interpretation and recommended configuration.<\/li>\n<li><strong>Example:<\/strong> OKE node pool upgrade behavior; you share cluster OCID and upgrade timeline.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Disaster recovery (DR) failover support<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> DR failover steps encounter OCI errors or limitations.<\/li>\n<li><strong>Why it fits:<\/strong> Support can help validate DR patterns and troubleshoot provider-side constraints.<\/li>\n<li><strong>Example:<\/strong> Cross-region replication lag plus failover errors; you include replication status and region details.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Certificate\/endpoint issues on OCI-managed front doors<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> TLS handshake failures after certificate rotation.<\/li>\n<li><strong>Why it fits:<\/strong> Vendor-assisted troubleshooting can accelerate resolution.<\/li>\n<li><strong>Example:<\/strong> Load balancer listener errors; you attach listener config export (sanitized) and client error logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Governance rollout blockers in a landing zone<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Organization-wide compartment\/tag policy rollout causes unexpected failures.<\/li>\n<li><strong>Why it fits:<\/strong> Support can clarify policy evaluation rules and service interactions.<\/li>\n<li><strong>Example:<\/strong> Tag defaults or IAM policy changes break automation; you include policy snippets (sanitized) and errors.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Support Requests is a workflow capability rather than a \u201cfeature-rich\u201d compute service. The most important features are about creating high-quality cases and managing them securely.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Create and submit support requests (cases\/incidents)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lets you open a request with structured fields such as service, category, severity, and description.<\/li>\n<li><strong>Why it matters:<\/strong> Correct categorization reduces time-to-triage.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster routing and fewer back-and-forth questions.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Availability depends on your support entitlement; some tenancies or user roles may not see the option.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Severity and impact classification<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows you to indicate business impact\/urgency.<\/li>\n<li><strong>Why it matters:<\/strong> Support response and escalation often depends on severity definitions.<\/li>\n<li><strong>Practical benefit:<\/strong> Aligns provider engagement with incident criticality.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Misclassifying severity can slow resolution or trigger reclassification. Follow Oracle\u2019s severity definitions for your plan (verify in official docs).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Attachments (logs, screenshots, exports)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Upload evidence to support threads.<\/li>\n<li><strong>Why it matters:<\/strong> OCI issues are often diagnosable only with precise identifiers and logs.<\/li>\n<li><strong>Practical benefit:<\/strong> Reduces time spent requesting basic information.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Attachment size\/type limits may apply; sanitize secrets and sensitive data before uploading.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Threaded communication and updates<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides a back-and-forth conversation thread with Oracle Support.<\/li>\n<li><strong>Why it matters:<\/strong> Keeps all communications in a single audited context.<\/li>\n<li><strong>Practical benefit:<\/strong> Smooth handoffs between shifts and teams.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Don\u2019t rely on it as a replacement for internal incident comms; integrate with your internal incident channel.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Request tracking and status<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Shows case status (open\/in progress\/waiting\/customer action\/closed) and history.<\/li>\n<li><strong>Why it matters:<\/strong> Helps incident commanders manage escalations and stakeholder updates.<\/li>\n<li><strong>Practical benefit:<\/strong> Clear accountability for next actions.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Status semantics differ across support organizations; interpret using Oracle\u2019s definitions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy-aware context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Associates requests with your Oracle Cloud tenancy and identity.<\/li>\n<li><strong>Why it matters:<\/strong> Enables Oracle to access tenant-side metadata and route appropriately.<\/li>\n<li><strong>Practical benefit:<\/strong> Less manual identity verification compared to email-based support.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Support still needs precise resource identifiers (OCIDs, region) for deep investigation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Limit increase and governance-related requests<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Supports operational tasks such as service limit increases and account configuration help (subject to Oracle processes).<\/li>\n<li><strong>Why it matters:<\/strong> Limits are a frequent blocker during growth.<\/li>\n<li><strong>Practical benefit:<\/strong> A standardized, trackable pathway for capacity enablement.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Not all limits are adjustable; approval may require justification and time.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">API\/automation (where available)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Some Oracle Cloud environments provide APIs\/SDKs to list\/create\/manage incidents programmatically (often associated with OCI incident management services).<\/li>\n<li><strong>Why it matters:<\/strong> Enables integration with ITSM (ServiceNow\/Jira), ChatOps, or automated incident creation.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster, standardized case creation with consistent metadata.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> API availability, permissions, and schemas must be verified in official docs for your tenancy\/support plan before implementation.<\/li>\n<\/ul>\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 architecture<\/h3>\n\n\n\n<p>At a high level, Support Requests works like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>A user (or automation) authenticates to Oracle Cloud using IAM.<\/li>\n<li>The user opens a Support Request in the OCI Console (or via an API where available).<\/li>\n<li>The request is submitted to Oracle Support\u2019s incident system.<\/li>\n<li>Oracle Support responds with questions, status updates, or remediation steps.<\/li>\n<li>The customer uploads additional evidence or confirms resolution.<\/li>\n<li>The case is closed and retained for history\/audit.<\/li>\n<\/ol>\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>Control-plane actions:<\/strong> create\/update requests, add attachments, change severity (subject to policy), close requests.<\/li>\n<li><strong>Data shared:<\/strong> user-entered description, metadata, and attachments provided by the customer.<\/li>\n<li><strong>What Oracle can see:<\/strong> depends on the issue and Oracle\u2019s internal tooling; always include OCIDs and timestamps to enable investigation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services<\/h3>\n\n\n\n<p>Support Requests often sits in the middle of these operational loops:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Audit<\/strong>: who created\/updated requests or performed the actions that led to the incident<\/li>\n<li><strong>Logging \/ Monitoring<\/strong>: evidence collection (graphs, log excerpts)<\/li>\n<li><strong>Resource Manager \/ Terraform<\/strong>: provisioning error outputs and plan\/apply logs<\/li>\n<li><strong>Notifications \/ Alarms<\/strong>: incident detection that triggers SR creation<\/li>\n<li><strong>Compartments\/Tags<\/strong>: identifying ownership and environment quickly<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud IAM and tenancy identity<\/li>\n<li>OCI Console<\/li>\n<li>Oracle Support systems and entitlements<\/li>\n<\/ul>\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 Oracle Cloud authentication (federated SSO or local users)<\/li>\n<li>Authorization is controlled by IAM policies and support entitlements<\/li>\n<li>Least privilege is recommended: only a subset of users should be able to create high-severity cases or manage all cases<\/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>Console access is over HTTPS<\/li>\n<li>Attachments and case metadata are transmitted over secure channels<\/li>\n<li>No customer VCN routing is needed to \u201creach\u201d Support Requests (it\u2019s not in your VCN)<\/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>Audit<\/strong> for tracking who changed critical resources during the incident window.<\/li>\n<li>Maintain internal incident records (ticket IDs, timestamps, severity) and cross-reference the Oracle Support Request ID.<\/li>\n<li>Tag resources consistently so you can quickly provide impacted compartment\/resource context.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Engineer \/ SRE] --&gt;|OCI Console| C[Support Requests]\n  C --&gt;|Create\/Update Case| OS[Oracle Support System]\n  OS --&gt;|Responses \/ Actions| C\n  C --&gt; U\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Customer[\"Customer Environment (OCI Tenancy)\"]\n    IAM[IAM: Users \/ Groups \/ Federation]\n    AUD[Audit]\n    MON[Monitoring &amp; Alarms]\n    LOG[Logging]\n    ITSM[ITSM: ServiceNow\/Jira (optional)]\n    RUN[Runbooks \/ Incident Channel]\n  end\n\n  subgraph OCI[\"Oracle Cloud Console &amp; APIs\"]\n    SR[Support Requests (Console workflow)]\n    API[Incident\/Support API (if enabled)]\n  end\n\n  subgraph Oracle[\"Oracle Support\"]\n    TRI[Support Triage]\n    ENG[Service Engineering \/ Ops]\n  end\n\n  IAM --&gt; SR\n  IAM --&gt; API\n\n  MON --&gt; RUN\n  LOG --&gt; RUN\n  AUD --&gt; RUN\n\n  RUN --&gt; SR\n  ITSM --&gt;|Link SR ID| RUN\n\n  SR --&gt; TRI\n  API --&gt; TRI\n  TRI --&gt; ENG\n  ENG --&gt; TRI\n  TRI --&gt; SR\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<p>Before you can use Support Requests effectively, confirm these prerequisites.<\/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 tenancy<\/strong><\/li>\n<li>A <strong>support entitlement\/plan<\/strong> that allows opening support requests  <\/li>\n<li>If you do not see Support Requests in the console, it may be due to plan level or permissions (verify in official docs and with your account administrator).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to access Support Requests in the OCI Console (or relevant API).<\/li>\n<li>Recommended: a dedicated group such as <code>Support-Request-Admins<\/code> with controlled membership.<\/li>\n<li>IAM policy syntax and resource types can vary; <strong>verify the current policy reference<\/strong> in Oracle Cloud docs for \u201csupport incidents\u201d \/ \u201cincident management\u201d.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Generally, support access is tied to your Oracle Cloud subscription and support plan.<\/li>\n<li>Some free-tier or trial accounts may have limited support options (verify for your account).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools (optional but strongly recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access<\/li>\n<li>OCI CLI for evidence collection (optional): https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/li>\n<li>A standard way to capture and store incident evidence internally (ticketing system, shared drive with access control)<\/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>Support Requests is tenancy-scoped; your issues will usually be region-specific. Know the impacted region(s).<\/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>Support Requests itself may have practical limits (attachments, maximum text, etc.). Verify current limits in official docs if you plan to standardize evidence uploads.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (for better cases)<\/h3>\n\n\n\n<p>To produce high-quality support requests, you typically need:\n&#8211; <strong>Audit<\/strong> enabled (default in many tenancies)\n&#8211; <strong>Logging\/Monitoring<\/strong> configured for your workloads (service logs, custom logs, alarms)<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Support Requests is not usually priced like a metered OCI data-plane service (e.g., OCPU-hours). Instead, cost is driven by your <strong>Oracle Cloud support plan\/entitlement<\/strong> and the operational overhead of running incident management.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Current pricing model (how to think about it)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Support plan based:<\/strong> The ability to open and manage Support Requests is typically tied to an Oracle Cloud support offering and your contract\/subscription terms.<\/li>\n<li><strong>No per-ticket fee in typical cloud support models:<\/strong> Many enterprise cloud support offerings do not charge \u201cper case\u201d but include case management within the support subscription. <strong>Verify your specific agreement<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p>Because support pricing can depend on:\n&#8211; Pay-as-you-go vs contracted\/Universal Credits\n&#8211; Support level (basic vs premium tiers)\n&#8211; Region and service portfolio\n&#8211; Enterprise agreements and negotiated terms<\/p>\n\n\n\n<p>\u2026you should rely on official Oracle pricing\/support pages and your contract.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing resources (start here)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud pricing landing page: https:\/\/www.oracle.com\/cloud\/pricing\/<\/li>\n<li>Oracle Cloud Cost Estimator (calculator): https:\/\/www.oracle.com\/cloud\/costestimator.html<\/li>\n<li>Oracle Cloud support information (plan details): https:\/\/www.oracle.com\/cloud\/support\/<br\/>\n  (If this URL changes, use Oracle\u2019s site search for \u201cOracle Cloud Support\u201d.)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions to consider<\/h3>\n\n\n\n<p>Even if Support Requests itself isn\u2019t metered per use, your total cost is influenced by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Support plan cost<\/strong> (contractual)<\/li>\n<li><strong>Operational labor cost<\/strong> (time to prepare evidence, respond to questions)<\/li>\n<li><strong>Log storage and observability costs<\/strong> (Logging ingestion, archive storage, APM\u2014depends on what you attach and retain)<\/li>\n<li><strong>Network egress<\/strong> (if you export logs or packet captures to external tools before attaching\/summarizing them)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Free tier\/trial accounts may have limited support channels and response expectations. Verify what is included for your account type in official docs\/support policy pages.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Uploading large logs\/screenshots can encourage \u201cover-sharing.\u201d This can create:<\/li>\n<li>security review overhead (redaction)<\/li>\n<li>storage and retention overhead (internal and external)<\/li>\n<li>slower triage if the case is noisy rather than focused<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost optimization strategies<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standardize what to capture: OCIDs, timestamps, region, request IDs, error codes, minimal log extracts.<\/li>\n<li>Use <strong>links to internal evidence<\/strong> where allowed (and secure), rather than uploading entire raw datasets.<\/li>\n<li>Train teams to classify severity correctly to avoid unnecessary escalation churn.<\/li>\n<li>Use internal runbooks to eliminate common, self-fixable issues before opening a case.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (qualitative)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A small team on a basic paid Oracle Cloud setup:<\/li>\n<li>Support Requests access is typically included with the support entitlement.<\/li>\n<li>Primary cost is engineering time and any observability services used to gather evidence.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations (qualitative)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A regulated enterprise running 24&#215;7 production:<\/li>\n<li>Support plan may be a meaningful contractual line item.<\/li>\n<li>Additional cost drivers include:<ul>\n<li>centralized logging retention<\/li>\n<li>incident tooling integrations<\/li>\n<li>on-call operational workload<\/li>\n<li>governance processes (approvals, evidence handling)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Create a <strong>well-formed Oracle Cloud Support Request<\/strong> for a realistic, low-risk scenario (a non-production guidance request or a limit increase inquiry), attach sanitized evidence, and learn how to track and operationalize the case.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Gather the minimum diagnostic context Oracle Support typically needs.<\/li>\n<li>Create a Support Request in the Oracle Cloud Console.<\/li>\n<li>Add a follow-up update with structured details and (optional) an attachment.<\/li>\n<li>Validate you can track status and reference the Support Request ID internally.<\/li>\n<li>Learn troubleshooting tips and cleanup\/closure best practices.<\/li>\n<\/ol>\n\n\n\n<p>This lab is designed to be safe: you will not change production resources.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare incident context (what to collect before you open the case)<\/h3>\n\n\n\n<p><strong>Why this matters:<\/strong> The fastest support outcomes happen when the first message contains all critical identifiers.<\/p>\n\n\n\n<p>Collect the following in a simple text file (internal only), then paste the relevant subset into the Support Request:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tenancy name<\/strong> (and tenancy OCID if your org uses it internally)<\/li>\n<li><strong>Impacted region(s)<\/strong> (example: <code>us-ashburn-1<\/code>)<\/li>\n<li><strong>Compartment name(s)<\/strong> (example: <code>Prod-Network<\/code>, <code>Dev-App<\/code>)<\/li>\n<li><strong>Resource OCIDs<\/strong> (example: instance OCID, VCN OCID, load balancer OCID)<\/li>\n<li><strong>Time window<\/strong> with timezone (example: <code>2026-04-16 13:05\u201313:20 UTC<\/code>)<\/li>\n<li><strong>What changed<\/strong> (deployments, Terraform apply, policy updates)<\/li>\n<li><strong>Exact error messages<\/strong> and where they appeared (Console, CLI, SDK)<\/li>\n<li><strong>Request IDs<\/strong> if shown in error messages<\/li>\n<li><strong>Business impact<\/strong> and whether a workaround exists<\/li>\n<li><strong>Contact method<\/strong> and on-call details (per your policy)<\/li>\n<\/ul>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have a clean problem statement and identifiers ready, without secrets.<\/p>\n\n\n\n<p><strong>Verification checklist (quick):<\/strong>\n&#8211; No passwords, API keys, private keys, or session tokens included\n&#8211; OCIDs and timestamps included\n&#8211; One paragraph describing impact and what you need from Oracle<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: (Optional) Gather lightweight evidence from OCI without exporting sensitive data<\/h3>\n\n\n\n<p>If your issue involves a specific OCI resource, gather minimal metadata.<\/p>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<p><strong>A) Get the OCID of an instance (Console)<\/strong>\n1. Open <strong>Compute<\/strong> \u2192 <strong>Instances<\/strong>\n2. Click the instance\n3. Copy the <strong>OCID<\/strong> and note the region<\/p>\n\n\n\n<p><strong>B) Capture a provisioning\/work request ID (Console)<\/strong>\n&#8211; If an OCI operation failed, look for a <strong>work request<\/strong> link or error banner containing an ID.\n&#8211; Copy it; support often uses it to trace backend operations.<\/p>\n\n\n\n<p><strong>C) Capture Audit events (Console)<\/strong>\n1. Open <strong>Governance &amp; Administration<\/strong> \u2192 <strong>Audit<\/strong>\n2. Filter the time window and relevant compartments\n3. Identify events that coincide with the failure (policy changes, resource updates)\n4. Copy event IDs or export minimal details (follow your org policy)<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have identifiers that help support correlate the issue.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create a Support Request in the Oracle Cloud Console<\/h3>\n\n\n\n<p><strong>Note:<\/strong> Console navigation labels can vary slightly. Common entry points include <strong>Help<\/strong> (top bar) \u2192 <strong>Support<\/strong> \u2192 <strong>Support Requests<\/strong>.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Sign in to the <strong>Oracle Cloud Console<\/strong>.<\/li>\n<li>Open the <strong>Help<\/strong> menu (top-right in many console layouts).<\/li>\n<li>Select <strong>Support<\/strong> or <strong>Support Requests<\/strong>.<\/li>\n<li>Click <strong>Create Support Request<\/strong> (or similar).<\/li>\n<\/ol>\n\n\n\n<p>Fill in the form carefully:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Service\/Product:<\/strong> Choose the OCI service involved (Compute, Networking, IAM, etc.)<\/li>\n<li><strong>Problem type\/category:<\/strong> Choose the closest match<\/li>\n<li><strong>Severity:<\/strong> Choose based on impact and Oracle\u2019s definitions (verify in your support plan docs)<\/li>\n<li><strong>Summary:<\/strong> One sentence, include region and symptom<br\/>\n  Example: <code>us-ashburn-1: Terraform apply fails with LimitExceeded for public IPs<\/code><\/li>\n<li><strong>Description:<\/strong> Use a structured template (copy\/paste friendly):<\/li>\n<\/ul>\n\n\n\n<p>Suggested template:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What happened:<\/strong><br\/>\n  (1\u20133 sentences)<\/li>\n<li><strong>Impact:<\/strong><br\/>\n  (who\/what is affected; prod vs dev)<\/li>\n<li><strong>When:<\/strong><br\/>\n  (timestamps + timezone)<\/li>\n<li><strong>Where:<\/strong><br\/>\n  (region, compartment, resource OCIDs)<\/li>\n<li><strong>What changed recently:<\/strong><br\/>\n  (deployments, policy edits, scaling, network changes)<\/li>\n<li><strong>What you already tried:<\/strong><br\/>\n  (to avoid repeated steps)<\/li>\n<li><strong>What you need from Oracle:<\/strong><br\/>\n  (limit increase, confirmation of platform issue, guidance, escalation)<\/li>\n<\/ul>\n\n\n\n<ol class=\"wp-block-list\" start=\"5\">\n<li>Submit the Support Request.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A new Support Request is created and you receive a <strong>Support Request ID<\/strong> (case\/incident number).<\/p>\n\n\n\n<p><strong>Verification steps:<\/strong>\n&#8211; Confirm the request appears in your <strong>Support Requests<\/strong> list.\n&#8211; Copy the Support Request ID into your internal ticket\/incident record.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Add a follow-up update with targeted details (and optional attachment)<\/h3>\n\n\n\n<p>Within the Support Request thread:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>Add a message that includes:\n   &#8211; OCIDs\n   &#8211; request\/work request IDs\n   &#8211; timestamps\n   &#8211; any new findings since creation<\/p>\n<\/li>\n<li>\n<p>If you attach a file:\n   &#8211; Prefer small, targeted files (a single screenshot, a short log excerpt)\n   &#8211; Redact secrets\n   &#8211; Use consistent filenames, e.g.:<\/p>\n<ul>\n<li><code>error-banner-2026-04-16-1307UTC.png<\/code><\/li>\n<li><code>terraform-apply-excerpt.txt<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> The case has enough context for Oracle Support to proceed without requesting basic details.<\/p>\n\n\n\n<p><strong>Verification steps:<\/strong>\n&#8211; Confirm the attachment is visible in the request.\n&#8211; Confirm your comment appears in the timeline\/thread.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Operationalize the Support Request (make it useful to your team)<\/h3>\n\n\n\n<p>In your internal incident process:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Link the Support Request ID in:<\/li>\n<li>incident channel topic<\/li>\n<li>ITSM ticket<\/li>\n<li>post-incident review doc<\/li>\n<li>Define who owns communication with Oracle Support (single-threaded ownership avoids conflicting responses).<\/li>\n<li>Track:<\/li>\n<li>next action required (Oracle vs customer)<\/li>\n<li>target response times (per your plan)<\/li>\n<li>escalation steps (if severity needs adjustment)<\/li>\n<\/ul>\n\n\n\n<p><strong>Expected outcome:<\/strong> Your organization can collaborate around the case without confusion.<\/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 this checklist to confirm the lab succeeded:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You can see the Support Request in the OCI Console.<\/li>\n<li>You have a Support Request ID recorded internally.<\/li>\n<li>The request includes region + OCIDs + timestamps.<\/li>\n<li>You can add a follow-up comment.<\/li>\n<li>You can identify whether the case is waiting on Oracle or waiting on you.<\/li>\n<\/ul>\n\n\n\n<p>If any item fails, use the troubleshooting section below.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p>Common issues and realistic fixes:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>You can\u2019t find \u201cSupport Requests\u201d in the console<\/strong>\n   &#8211; Cause: insufficient IAM permissions or support entitlement.\n   &#8211; Fix: verify you are using the correct tenancy and region context; check with your tenancy administrators; confirm your support plan includes case creation.<\/p>\n<\/li>\n<li>\n<p><strong>You can view requests but cannot create\/update<\/strong>\n   &#8211; Cause: IAM policy grants read\/inspect but not manage\/update.\n   &#8211; Fix: request least-privilege access for support request management per Oracle\u2019s IAM policy reference (verify in official docs).<\/p>\n<\/li>\n<li>\n<p><strong>Attachment upload fails<\/strong>\n   &#8211; Cause: file too large, unsupported type, network interruption, or security controls.\n   &#8211; Fix: reduce file size, compress text logs, split into smaller parts, or paste minimal excerpts into the message.<\/p>\n<\/li>\n<li>\n<p><strong>Oracle Support asks for details you already provided<\/strong>\n   &#8211; Cause: information buried in long text or missing key identifiers.\n   &#8211; Fix: reply with a short bullet list of OCIDs, region, exact time window, and a single \u201cwhat you need\u201d sentence.<\/p>\n<\/li>\n<li>\n<p><strong>You\u2019re unsure about severity<\/strong>\n   &#8211; Fix: follow your internal incident severity mapping and Oracle\u2019s official severity definitions; if business impact changes, ask support about reclassification.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>Because this lab creates an operational artifact (a support case), \u201ccleanup\u201d means closing it appropriately:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If the request was only for practice, reply stating:  <\/li>\n<li>it was created for training\/testing (if acceptable by your org)  <\/li>\n<li>no further action is required  <\/li>\n<li>request closure<\/li>\n<li>If it is a real issue:<\/li>\n<li>confirm resolution steps and timestamps<\/li>\n<li>document the root cause (if known)<\/li>\n<li>close the request after verifying stability<\/li>\n<li>Update internal runbooks with lessons learned (what evidence was most useful, what to include next time).<\/li>\n<\/ul>\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 (operational design)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat Support Requests as part of your <strong>incident management architecture<\/strong>:<\/li>\n<li>alarms \u2192 triage \u2192 mitigation \u2192 provider escalation \u2192 resolution \u2192 review<\/li>\n<li>Standardize a \u201csupport request packet\u201d template:<\/li>\n<li>region, OCIDs, time window, impact, what changed, what you need<\/li>\n<li>For multi-region systems, open one case per distinct platform issue unless Oracle advises otherwise.<\/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>Use least privilege:<\/li>\n<li>allow most engineers to <strong>view<\/strong> cases<\/li>\n<li>restrict <strong>create\/update\/severity change<\/strong> to on-call leads or platform ops<\/li>\n<li>Use a dedicated group for support case management and review membership regularly.<\/li>\n<li>Avoid shared accounts; use individual identities (federated SSO preferred).<\/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>Don\u2019t over-collect logs \u201cjust in case.\u201d<\/li>\n<li>Store full raw evidence internally (securely) and provide targeted excerpts to Oracle Support.<\/li>\n<li>Use tagging\/compartment discipline to reduce time-to-identify ownership.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices (time-to-resolution)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Include request\/work request IDs where possible.<\/li>\n<li>Provide a clear \u201cstart time\u201d of the incident in UTC.<\/li>\n<li>State what you need from Oracle in one sentence (limit increase, confirmation, workaround, bug investigation).<\/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>Define escalation rules:<\/li>\n<li>when to open a case<\/li>\n<li>when to increase severity<\/li>\n<li>when to switch to phone\/urgent channels (depends on support plan)<\/li>\n<li>Maintain continuity:<\/li>\n<li>one owner for Oracle communications<\/li>\n<li>consistent updates after each investigation step<\/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>Link the Support Request ID into your internal incident record.<\/li>\n<li>Record every Oracle recommendation and your outcome.<\/li>\n<li>After closure, update:<\/li>\n<li>runbooks<\/li>\n<li>Terraform modules\/guardrails<\/li>\n<li>monitoring alerts (if detection was late)<\/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>Ensure every production resource has:<\/li>\n<li>environment tag (prod\/dev)<\/li>\n<li>owner tag (team)<\/li>\n<li>application tag<\/li>\n<li>In Support Requests, always reference:<\/li>\n<li>compartment name<\/li>\n<li>tags if helpful<\/li>\n<li>OCIDs for precision<\/li>\n<\/ul>\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>Support Requests access is governed by:<\/li>\n<li>Oracle Cloud IAM authentication<\/li>\n<li>IAM authorization (policies)<\/li>\n<li>support entitlement\/plan<\/li>\n<\/ul>\n\n\n\n<p><strong>Recommendation:<\/strong> implement role separation:\n&#8211; View-only for broad audiences\n&#8211; Case creation\/update for on-call\/platform roles\n&#8211; Administrative control for tenancy admins<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Console communications use HTTPS.<\/li>\n<li>Attachments and metadata are transmitted securely.<\/li>\n<li>For details on encryption at rest and internal handling, <strong>verify in official Oracle support\/security documentation<\/strong> relevant to your service and contract.<\/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>Support Requests is accessed via OCI Console over the public internet (or via corporate egress).<\/li>\n<li>Consider:<\/li>\n<li>corporate proxy controls<\/li>\n<li>conditional access (if using identity federation)<\/li>\n<li>logging access to the console<\/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>Do not paste or attach:<\/li>\n<li>API private keys<\/li>\n<li>passwords<\/li>\n<li>tokens<\/li>\n<li>connection strings with credentials<\/li>\n<li>Redact:<\/li>\n<li>customer PII<\/li>\n<li>sensitive business data<\/li>\n<li>internal IP addressing if restricted by policy (coordinate with your security team)<\/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>Track changes during the incident window using <strong>Audit<\/strong>.<\/li>\n<li>Keep internal records of:<\/li>\n<li>who opened the case<\/li>\n<li>what data was shared<\/li>\n<li>who approved sharing (for regulated environments)<\/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>Ensure your support engagement follows:<\/li>\n<li>data handling policies<\/li>\n<li>retention policies<\/li>\n<li>regulatory requirements (HIPAA, PCI, SOC, etc.)<\/li>\n<li>For regulated data, prefer minimal excerpts and anonymized identifiers where possible.<\/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>Uploading full debug bundles containing secrets<\/li>\n<li>Sharing production database exports to illustrate an application error<\/li>\n<li>Allowing broad \u201cmanage all support requests\u201d permissions without review<\/li>\n<li>Not correlating incident actions with Audit logs (reduces investigation quality)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations (operational)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create a redaction checklist and make it part of the runbook.<\/li>\n<li>Require peer review for attachments in high-sensitivity environments.<\/li>\n<li>Use compartment\/tag-based ownership to prevent accidental disclosure across teams.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Support Requests is operationally critical, but there are practical constraints.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Support entitlement dependency:<\/strong> If your plan doesn\u2019t include full support, you may not be able to open requests or may have limited severity options.<\/li>\n<li><strong>IAM visibility:<\/strong> Users might not see the Support Requests UI due to missing permissions.<\/li>\n<li><strong>Attachment limits:<\/strong> File size\/type restrictions can block uploads; plan for log excerpt workflows.<\/li>\n<li><strong>Not a substitute for internal incident tooling:<\/strong> Support Requests is provider-facing; you still need internal incident coordination.<\/li>\n<li><strong>Severity definitions are contractual:<\/strong> Misuse can result in reclassification; align with Oracle\u2019s definitions.<\/li>\n<li><strong>Region\/service ambiguity slows triage:<\/strong> Always specify region(s) and service(s).<\/li>\n<li><strong>Case ownership confusion:<\/strong> Multiple responders from your org can create conflicting narratives; designate a single owner.<\/li>\n<li><strong>Timezones:<\/strong> Failing to use UTC or specify timezone is a classic delay factor.<\/li>\n<li><strong>Sensitive data risk:<\/strong> Over-sharing logs can create security\/compliance issues.<\/li>\n<li><strong>API\/automation variability:<\/strong> If you plan automation, verify current OCI incident\/support API capabilities, required permissions, and schemas in official docs.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Support Requests is the provider-native route for Oracle Cloud issues, but it sits among related options.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Alternatives (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In Oracle Cloud:<\/strong> internal governance tools (Audit, Logging, Monitoring) are not replacements; they are inputs. My Oracle Support (MOS) may be used for broader Oracle product support depending on your relationship and products.<\/li>\n<li><strong>Other clouds:<\/strong> AWS Support Center, Azure Support Requests, Google Cloud Support Cases.<\/li>\n<li><strong>Self-managed:<\/strong> Jira Service Management, ServiceNow, Zendesk\u2014good for internal workflow, but not a replacement for provider escalation.<\/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>Oracle Cloud <strong>Support Requests<\/strong><\/td>\n<td>OCI incidents, limit increases, provider-side investigations<\/td>\n<td>Native to OCI Console, tenancy-aware, structured routing, official record<\/td>\n<td>Depends on entitlement; requires good evidence hygiene<\/td>\n<td>When OCI services\/limits\/platform behavior are involved<\/td>\n<\/tr>\n<tr>\n<td>Oracle <strong>My Oracle Support (MOS)<\/strong> (if applicable)<\/td>\n<td>Organizations supporting multiple Oracle products (cloud + software)<\/td>\n<td>Consolidated Oracle support ecosystem<\/td>\n<td>May be separate workflow; may not be the primary path for some OCI-only tasks<\/td>\n<td>When your org\u2019s support process is MOS-centric or includes non-OCI products<\/td>\n<\/tr>\n<tr>\n<td>OCI <strong>Audit \/ Logging \/ Monitoring<\/strong><\/td>\n<td>Detection and evidence collection<\/td>\n<td>Powerful for internal troubleshooting and governance<\/td>\n<td>Does not escalate to Oracle by itself<\/td>\n<td>Use before and alongside Support Requests<\/td>\n<\/tr>\n<tr>\n<td>AWS Support Center Cases<\/td>\n<td>AWS environments<\/td>\n<td>Mature workflow and integrations<\/td>\n<td>Not relevant to OCI<\/td>\n<td>Choose if workload runs on AWS<\/td>\n<\/tr>\n<tr>\n<td>Azure Support Requests<\/td>\n<td>Azure environments<\/td>\n<td>Native to Azure portal<\/td>\n<td>Not relevant to OCI<\/td>\n<td>Choose if workload runs on Azure<\/td>\n<\/tr>\n<tr>\n<td>Google Cloud Support Cases<\/td>\n<td>GCP environments<\/td>\n<td>Native workflow<\/td>\n<td>Not relevant to OCI<\/td>\n<td>Choose if workload runs on GCP<\/td>\n<\/tr>\n<tr>\n<td>ServiceNow \/ Jira Service Management<\/td>\n<td>Internal ITSM workflow<\/td>\n<td>Great for approvals, routing, internal SLAs<\/td>\n<td>Not provider-native; still need OCI Support Requests to engage Oracle<\/td>\n<td>Choose for internal incident\/ticket governance, then link to Support Request<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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 (regulated financial services)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A production payment API experiences intermittent timeouts. Monitoring shows spikes in latency and occasional 5xx from a managed load balancer layer. The incident must be handled with strict audit and evidence controls.<\/li>\n<li><strong>Proposed architecture (operational):<\/strong><\/li>\n<li>Alarms trigger incident channel + ITSM ticket<\/li>\n<li>SRE gathers:<ul>\n<li>load balancer OCID, backend set info (sanitized)<\/li>\n<li>work request IDs for recent changes<\/li>\n<li>Monitoring graphs (latency, backend errors)<\/li>\n<li>Audit events around deployment window<\/li>\n<\/ul>\n<\/li>\n<li>SRE opens an Oracle Cloud <strong>Support Request<\/strong> with:<ul>\n<li>UTC time window<\/li>\n<li>region<\/li>\n<li>OCIDs<\/li>\n<li>impact statement and severity aligned to the support plan<\/li>\n<\/ul>\n<\/li>\n<li>All provider communication is done by the incident commander; updates are mirrored into ITSM.<\/li>\n<li><strong>Why Support Requests was chosen:<\/strong> It is the official vendor escalation channel, tenancy-aware, and fits compliance evidence requirements.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Faster provider-side correlation using work request IDs<\/li>\n<li>Documented remediation steps<\/li>\n<li>Strong post-incident evidence for audits<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example (SaaS platform)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A fast-growing SaaS hits a service limit while onboarding new customers. Deployments fail in CI\/CD with a \u201climit exceeded\u201d error.<\/li>\n<li><strong>Proposed architecture (operational):<\/strong><\/li>\n<li>DevOps lead collects the exact error, region, and current planned capacity<\/li>\n<li>Opens a Support Request requesting a limit increase with:<ul>\n<li>justification (growth plan)<\/li>\n<li>target limits required<\/li>\n<li>timeline<\/li>\n<\/ul>\n<\/li>\n<li>Meanwhile, the team implements a temporary workaround (reuse resources, reduce parallel environments).<\/li>\n<li><strong>Why Support Requests was chosen:<\/strong> It\u2019s the formal path to increase limits and keep scaling.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Limit increase approved (if eligible)<\/li>\n<li>Reduced deployment friction<\/li>\n<li>A repeatable runbook for future scale events<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>What is Oracle Cloud Support Requests used for?<\/strong><br\/>\nIt\u2019s used to create and manage official support cases with Oracle for OCI issues, questions that require vendor input, limit increase requests, and incident response coordination.<\/p>\n\n\n\n<p>2) <strong>Is Support Requests the same as My Oracle Support (MOS)?<\/strong><br\/>\nNot necessarily. MOS is a broader Oracle support portal used across many Oracle products. OCI\u2019s console-based Support Requests is the cloud-operations-friendly workflow for tenancy-related issues. Your organization may use one or both depending on contracts and products\u2014verify your support process.<\/p>\n\n\n\n<p>3) <strong>Do I need a paid support plan to create Support Requests?<\/strong><br\/>\nIn many cases, yes\u2014case creation and severity options depend on your support entitlement. If you can\u2019t access it, verify your plan and permissions.<\/p>\n\n\n\n<p>4) <strong>Why can\u2019t I see Support Requests in the OCI Console?<\/strong><br\/>\nCommon reasons: missing IAM permissions, using the wrong tenancy, or your account\/support plan doesn\u2019t include that feature. Confirm with your tenancy admins and Oracle account team.<\/p>\n\n\n\n<p>5) <strong>What information should I include in the first message?<\/strong><br\/>\nAt minimum: region, OCIDs, timestamps (UTC), exact error messages, what changed recently, and what you need from Oracle. Include work request IDs if present.<\/p>\n\n\n\n<p>6) <strong>Should I attach full logs?<\/strong><br\/>\nUsually no. Attach small, relevant excerpts or sanitized files. Keep full raw logs internally and provide excerpts unless Oracle explicitly requests more.<\/p>\n\n\n\n<p>7) <strong>Can I request service limit increases via Support Requests?<\/strong><br\/>\nOften yes, and it\u2019s a common reason to open a case. Not all limits are adjustable, and approvals may require justification and time.<\/p>\n\n\n\n<p>8) <strong>How do I choose severity?<\/strong><br\/>\nUse your internal incident severity mapping and Oracle\u2019s official severity definitions for your support plan. If impact changes, ask to reclassify.<\/p>\n\n\n\n<p>9) <strong>Is there an API to create support requests automatically?<\/strong><br\/>\nOracle has had incident\/support management APIs in some contexts. Availability and schemas can vary by tenancy and support plan. Verify in official OCI API documentation before building automation.<\/p>\n\n\n\n<p>10) <strong>Can multiple people collaborate on the same case?<\/strong><br\/>\nYes, but designate a single owner to avoid conflicting responses. Others can contribute evidence and drafts internally.<\/p>\n\n\n\n<p>11) <strong>Can I use Support Requests for security incidents?<\/strong><br\/>\nYes, if the incident involves OCI platform behavior or account-level concerns. Follow your internal security process and be careful not to share sensitive data unnecessarily.<\/p>\n\n\n\n<p>12) <strong>How do I speed up Oracle Support troubleshooting?<\/strong><br\/>\nProvide OCIDs, work request IDs, and a tight time window; specify whether the issue is ongoing; list what you already tried; keep the problem statement short and precise.<\/p>\n\n\n\n<p>13) <strong>What\u2019s the best way to handle attachments securely?<\/strong><br\/>\nRedact secrets and PII, minimize scope, and have a peer review step for high-sensitivity incidents.<\/p>\n\n\n\n<p>14) <strong>How do I link Support Requests with ITSM tools like ServiceNow\/Jira?<\/strong><br\/>\nA common pattern is to create an internal ticket and include the Oracle Support Request ID, plus periodic status updates. If you automate, verify APIs and permissions first.<\/p>\n\n\n\n<p>15) <strong>Should I close the Support Request when the issue is mitigated?<\/strong><br\/>\nClose it after you confirm stability and document the resolution. If Oracle provided guidance, summarize what worked before closure for future reference.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Support Requests<\/h2>\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>Oracle Cloud Infrastructure Documentation (main docs) \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/<\/td>\n<td>Starting point for all OCI services; search for \u201cContact Support\u201d \/ \u201cSupport Requests\u201d<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Contacting Support \/ Support Requests (OCI) \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/ (search within)<\/td>\n<td>Official steps and requirements can change; use this to confirm current UI flow and entitlements<\/td>\n<\/tr>\n<tr>\n<td>Official API docs<\/td>\n<td>OCI APIs (search for incident\/support management) \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/api\/<\/td>\n<td>If you plan automation, validate available endpoints and models<\/td>\n<\/tr>\n<tr>\n<td>Official CLI docs<\/td>\n<td>OCI CLI installation and usage \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/td>\n<td>Helps you collect evidence (OCIDs, configuration, errors) consistently<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Pricing \u2014 https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<td>Support pricing is usually tied to plan\/contract; start here for official commercial framing<\/td>\n<\/tr>\n<tr>\n<td>Official calculator<\/td>\n<td>Oracle Cloud Cost Estimator \u2014 https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Useful for understanding total environment cost drivers that often lead to support inquiries<\/td>\n<\/tr>\n<tr>\n<td>Official architecture<\/td>\n<td>OCI Architecture Center \u2014 https:\/\/www.oracle.com\/cloud\/architecture-center\/<\/td>\n<td>Reference architectures that reduce incidents and improve governance<\/td>\n<\/tr>\n<tr>\n<td>Official tutorials\/labs<\/td>\n<td>Oracle LiveLabs \u2014 https:\/\/apexapps.oracle.com\/pls\/apex\/f?p=133:1<\/td>\n<td>Hands-on labs for OCI services; helpful for building operational familiarity<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle Cloud YouTube channel \u2014 https:\/\/www.youtube.com\/@OracleCloudInfrastructure<\/td>\n<td>Product updates and operational guidance; search for support\/governance topics<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Oracle Cloud community\/blogs (verify accuracy)<\/td>\n<td>Real-world troubleshooting patterns; cross-check with official docs before adoption<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>DevOpsSchool.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> DevOps engineers, SREs, cloud engineers, platform teams<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> DevOps practices, cloud operations, governance workflows, incident response foundations<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>ScmGalaxy.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> DevOps beginners to intermediate practitioners<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> SCM\/CI\/CD fundamentals, operational practices, tooling ecosystems<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/www.scmgalaxy.com\/<\/p>\n<\/li>\n<li>\n<p><strong>CLoudOpsNow.in<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Cloud operations and support-focused engineers<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> CloudOps operations, monitoring, incident handling, governance basics<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/cloudopsnow.in\/<\/p>\n<\/li>\n<li>\n<p><strong>SreSchool.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> SREs, reliability engineers, operations leads<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> SRE principles, incident management, reliability practices, runbooks<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/sreschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>AiOpsSchool.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Operations teams exploring AIOps\/automation<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> AIOps concepts, automation, event correlation, operational analytics<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/aiopsschool.com\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>RajeshKumar.xyz<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps\/cloud training content (verify current offerings on site)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Engineers seeking practical DevOps and operations guidance<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/rajeshkumar.xyz\/<\/p>\n<\/li>\n<li>\n<p><strong>devopstrainer.in<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps tooling and practices training (verify current catalog)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Beginners to intermediate DevOps practitioners<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/devopstrainer.in\/<\/p>\n<\/li>\n<li>\n<p><strong>devopsfreelancer.com<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps consulting\/training-style guidance (verify services)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Teams needing hands-on DevOps help or mentoring<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/devopsfreelancer.com\/<\/p>\n<\/li>\n<li>\n<p><strong>devopssupport.in<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> Operational support and DevOps assistance (verify scope)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Ops teams needing practical support workflows<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/devopssupport.in\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>cotocus.com<\/strong><br\/>\n   &#8211; <strong>Likely service area:<\/strong> Cloud and DevOps consulting (verify current service lines)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> Landing zone setup, governance, operations process, CI\/CD, cost controls<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> Designing compartment\/tag strategy; building incident runbooks; integrating monitoring with ITSM<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/cotocus.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DevOpsSchool.com<\/strong><br\/>\n   &#8211; <strong>Likely service area:<\/strong> DevOps consulting and training services (verify current offerings)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> DevOps transformation, SRE practices, cloud operations enablement<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> Standardizing support escalation processes; operational readiness assessments; building CloudOps playbooks<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DEVOPSCONSULTING.IN<\/strong><br\/>\n   &#8211; <strong>Likely service area:<\/strong> DevOps and cloud consulting (verify current services)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> CI\/CD automation, infrastructure as code, monitoring\/logging setup, operational governance<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> Building a \u201csupport request packet\u201d process; setting up alerts and evidence collection; integrating support workflows into release management<br\/>\n   &#8211; <strong>Website URL:<\/strong> https:\/\/devopsconsulting.in\/<\/p>\n<\/li>\n<\/ol>\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 this service<\/h3>\n\n\n\n<p>To use Support Requests effectively, you should understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI fundamentals: regions, compartments, OCIDs<\/li>\n<li>IAM basics: users, groups, policies, federation<\/li>\n<li>Core governance tools: Audit, Logging, Monitoring<\/li>\n<li>Basic troubleshooting: reading error messages, correlating timestamps, change tracking<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after this service<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident management and SRE practices:<\/li>\n<li>severity definitions<\/li>\n<li>on-call handoffs<\/li>\n<li>post-incident reviews<\/li>\n<li>OCI observability deep dive:<\/li>\n<li>structured logging<\/li>\n<li>metrics and alarms<\/li>\n<li>tracing\/APM (if used)<\/li>\n<li>FinOps:<\/li>\n<li>cost reporting<\/li>\n<li>usage anomaly detection<\/li>\n<li>Automation:<\/li>\n<li>Infrastructure as Code (Terraform\/Resource Manager)<\/li>\n<li>(Optional) support case automation via APIs (verify availability first)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Cloud Operations Engineer<\/li>\n<li>DevOps Engineer<\/li>\n<li>Site Reliability Engineer (SRE)<\/li>\n<li>Platform Engineer<\/li>\n<li>Security Engineer (for cloud account\/security events)<\/li>\n<li>Technical Program Manager \/ Incident Manager (coordination and governance)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle\u2019s certification offerings evolve over time. For the most current OCI certification path, verify on Oracle University:\n&#8211; https:\/\/education.oracle.com\/<\/p>\n\n\n\n<p>Support Requests itself is usually not a standalone exam topic, but it is part of real operational readiness for OCI-certified engineers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build an internal \u201cSupport Request Packet\u201d template and runbook<\/li>\n<li>Create a checklist for evidence collection (OCIDs, work request IDs, UTC timestamps)<\/li>\n<li>Implement a tagging standard to accelerate ownership identification in incidents<\/li>\n<li>Set up alarms and an internal workflow that prompts \u201copen a Support Request\u201d when specific high-impact OCI errors occur<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Support Requests:<\/strong> Oracle Cloud Console workflow for opening and managing support cases with Oracle Support.<\/li>\n<li><strong>Tenancy:<\/strong> Your Oracle Cloud account boundary that contains compartments, IAM, and resources.<\/li>\n<li><strong>Compartment:<\/strong> Logical container for organizing OCI resources and applying access control.<\/li>\n<li><strong>OCID:<\/strong> Oracle Cloud Identifier; unique ID used to reference resources precisely.<\/li>\n<li><strong>Region:<\/strong> Geographic area where OCI services run (e.g., <code>us-ashburn-1<\/code>).<\/li>\n<li><strong>Severity:<\/strong> Classification of incident impact\/urgency per support plan definitions.<\/li>\n<li><strong>Work Request:<\/strong> An OCI asynchronous operation record used to track long-running actions (often referenced in failures).<\/li>\n<li><strong>Audit:<\/strong> OCI service that records API calls and key actions for governance and investigations.<\/li>\n<li><strong>ITSM:<\/strong> IT Service Management system (e.g., ServiceNow, Jira Service Management) used for internal ticketing and workflow.<\/li>\n<li><strong>Runbook:<\/strong> Documented operational procedure for diagnosing and resolving incidents.<\/li>\n<li><strong>Least privilege:<\/strong> Security principle of granting only the minimum permissions needed.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Oracle Cloud <strong>Support Requests<\/strong> is the official, tenancy-aware way to engage Oracle Support for OCI incidents, operational questions, and requests like service limit increases. It matters because it turns \u201cwe need provider help\u201d into a structured, auditable workflow aligned with Governance and Administration practices.<\/p>\n\n\n\n<p>In practice, success with Support Requests depends less on UI clicks and more on operational discipline: include regions, OCIDs, work request IDs, UTC timestamps, and a clear statement of impact and desired outcome\u2014while avoiding secrets and unnecessary data exposure.<\/p>\n\n\n\n<p>Cost is typically tied to your <strong>support plan\/contract<\/strong>, not per-ticket charges, but indirect costs (engineering time, observability retention) can be significant\u2014so standardize evidence collection and escalation paths.<\/p>\n\n\n\n<p>Use Support Requests when OCI services, limits, or platform behavior are involved and you need a formal vendor engagement record. Next, deepen your operational readiness by improving Audit\/Logging\/Monitoring usage and by building incident runbooks that consistently produce high-quality support cases.<\/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-915","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\/915","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=915"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/915\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=915"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=915"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}