{"id":928,"date":"2026-04-17T04:12:31","date_gmt":"2026-04-17T04:12:31","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-marketplace-guide-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace\/"},"modified":"2026-04-17T04:12:31","modified_gmt":"2026-04-17T04:12:31","slug":"oracle-cloud-marketplace-guide-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-marketplace-guide-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace\/","title":{"rendered":"Oracle Cloud Marketplace Guide Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Marketplace"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Marketplace<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Oracle Cloud <strong>Marketplace Guide<\/strong> is a practical guide to using <strong>Oracle Cloud Marketplace<\/strong>\u2014Oracle\u2019s catalog of third\u2011party and Oracle\u2011provided solutions that you can deploy into your Oracle Cloud Infrastructure (OCI) tenancy.<\/p>\n\n\n\n<p>In simple terms: <strong>Marketplace Guide<\/strong> helps you find prebuilt software (images, applications, and deployable stacks), accept the right terms, and launch it safely into your OCI environment without building everything from scratch.<\/p>\n\n\n\n<p>Technically, Oracle Cloud Marketplace is a console-driven (and in some cases API\/automation-assisted) distribution channel for software that typically deploys onto OCI services such as <strong>Compute<\/strong>, <strong>VCN networking<\/strong>, <strong>Block Volumes<\/strong>, <strong>OKE<\/strong>, and <strong>Resource Manager (Terraform)<\/strong>. Many listings require a subscription\/terms acceptance step, and pricing can include <strong>OCI infrastructure charges<\/strong>, <strong>publisher license charges<\/strong>, or both.<\/p>\n\n\n\n<p>The core problem Marketplace Guide solves: <strong>reducing time-to-value and deployment risk<\/strong> by using vetted, repeatable solution packages\u2014while still requiring you to architect for security, networking, IAM, cost control, and operations.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (important): \u201cMarketplace Guide\u201d is not generally presented as a standalone OCI product SKU; it\u2019s best understood as a <strong>guide to Oracle Cloud Marketplace<\/strong> capabilities and workflows. Verify current naming and scope in the official docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Marketplace Guide?<\/h2>\n\n\n\n<p><strong>Official purpose (scope)<\/strong><br\/>\nMarketplace Guide (Oracle Cloud Marketplace) exists to help customers discover, evaluate, procure\/subscribe to, and deploy software solutions on Oracle Cloud\u2014ranging from open-source images to commercial partner appliances and SaaS integrations.<\/p>\n\n\n\n<p><strong>Core capabilities (what you can do)<\/strong>\n&#8211; <strong>Browse and search listings<\/strong> (by category, publisher, pricing model, supported regions, and more).\n&#8211; <strong>Review listing details<\/strong> (architecture, prerequisites, license terms, support model, and deployment instructions).\n&#8211; <strong>Subscribe \/ accept terms<\/strong> for a listing (often required before deployment).\n&#8211; <strong>Deploy<\/strong> a solution into your tenancy, commonly via:\n  &#8211; <strong>VM images<\/strong> (launching a Compute instance from a Marketplace image)\n  &#8211; <strong>Resource Manager stacks<\/strong> (Terraform-based deployments)\n  &#8211; Other packaging models depending on the listing (availability varies; verify per listing)<\/p>\n\n\n\n<p><strong>Major components (conceptual)<\/strong>\n&#8211; <strong>Marketplace listing<\/strong>: The product page\/definition (publisher, versions, documentation, pricing, support).\n&#8211; <strong>Subscription\/terms acceptance<\/strong>: Your tenancy\u2019s acknowledgement of license terms for the listing.\n&#8211; <strong>Deployment mechanism<\/strong>: Image-based or stack-based deployment that creates OCI resources.\n&#8211; <strong>Billing relationship<\/strong>: Marketplace purchases may appear on your Oracle bill; the exact model depends on the listing (publisher-provided pricing vs BYOL vs free).<\/p>\n\n\n\n<p><strong>Service type<\/strong>\n&#8211; A <strong>catalog\/procurement and deployment portal<\/strong> integrated into OCI Console (and sometimes accessible via APIs\/automation, depending on feature support).<\/p>\n\n\n\n<p><strong>Scope: regional\/global\/tenancy<\/strong>\n&#8211; The <strong>Marketplace UI is effectively global<\/strong> in the sense you access it from the OCI Console.\n&#8211; <strong>Deployments are regional<\/strong>: the actual resources created (Compute, VCN, OKE, etc.) live in a chosen <strong>OCI region<\/strong> and <strong>compartment<\/strong>.\n&#8211; Subscriptions\/terms acceptance are generally <strong>tenancy-scoped<\/strong>, while deployments are <strong>compartment-scoped<\/strong> (governed by IAM policies).<\/p>\n\n\n\n<p><strong>How it fits into the Oracle Cloud ecosystem<\/strong>\nMarketplace Guide sits at the \u201csolution acquisition\u201d layer:\n&#8211; <strong>Marketplace<\/strong> provides solution packages.\n&#8211; <strong>IAM<\/strong> controls who can subscribe\/deploy.\n&#8211; <strong>Resource Manager<\/strong> (Terraform) and <strong>Compute<\/strong> perform the actual deployment.\n&#8211; <strong>Logging\/Auditing\/Monitoring<\/strong> provide operational governance after deployment.\n&#8211; <strong>Billing\/Cost Management<\/strong> tracks infrastructure usage and any marketplace charges.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Marketplace Guide?<\/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>Faster procurement and deployment<\/strong> than traditional vendor contracting + manual installs.<\/li>\n<li><strong>Lower project risk<\/strong> by using established solution packages with published deployment guidance.<\/li>\n<li><strong>Broader solution choice<\/strong>: security, networking, observability, data tools, DevOps tools, and industry apps.<\/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>Repeatable deployments<\/strong> using versioned images and\/or Infrastructure-as-Code stacks.<\/li>\n<li><strong>Reference architectures<\/strong> embedded in listings (varies by publisher).<\/li>\n<li><strong>Integration with OCI primitives<\/strong> (VCN, NSGs, IAM, Resource Manager).<\/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>Standardization<\/strong>: teams can converge on approved marketplace listings.<\/li>\n<li><strong>Support clarity<\/strong>: listings typically state who supports what (publisher vs Oracle vs community).<\/li>\n<li><strong>Lifecycle management<\/strong>: versioned artifacts, documentation, and sometimes upgrade paths (varies; verify per listing).<\/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>Centralized governance<\/strong>: control who can deploy what via compartments and IAM policies.<\/li>\n<li><strong>Auditable actions<\/strong>: subscription and deployment activities can be audited (via OCI Audit service).<\/li>\n<li><strong>Terms and licensing clarity<\/strong>: acceptance and billing models are explicit in listing terms.<\/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>Marketplace itself doesn\u2019t \u201cscale\u201d workloads\u2014OCI services do. But Marketplace Guide helps you pick architectures that scale (e.g., HA patterns, load balancers, cluster deployments) when publishers provide them.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Marketplace Guide<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need a <strong>production-ready starting point<\/strong> (images\/stacks) rather than building from scratch.<\/li>\n<li>You want to <strong>standardize<\/strong> deployments across multiple teams\/compartments.<\/li>\n<li>You want <strong>faster evaluation<\/strong> of tools (security appliances, monitoring stacks, CI\/CD tools).<\/li>\n<li>You have a governance model and want controlled self-service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You require <strong>fully custom builds<\/strong> and prefer hardened golden images built internally.<\/li>\n<li>Your compliance requires <strong>source code review<\/strong> and you can\u2019t accept third-party binaries\/images.<\/li>\n<li>The listing\u2019s <strong>support model, licensing, or region availability<\/strong> doesn\u2019t match your needs.<\/li>\n<li>You need a solution that Marketplace doesn\u2019t provide\u2014or provides only in a form that conflicts with your architecture (e.g., single-node deployments when you need HA).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Marketplace Guide used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Financial services<\/strong>: security appliances, SIEM integrations, hardened OS images (subject to compliance).<\/li>\n<li><strong>Healthcare<\/strong>: HIPAA-like controls and auditability (verify specific compliance needs).<\/li>\n<li><strong>Retail\/e-commerce<\/strong>: web platforms, WAF\/security, observability.<\/li>\n<li><strong>Manufacturing\/IoT<\/strong>: data ingestion pipelines, edge-related tools (often hybrid).<\/li>\n<li><strong>Public sector<\/strong>: controlled catalogs, compartment-based governance.<\/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 teams building \u201cpaved roads\u201d<\/li>\n<li>DevOps\/SRE teams standardizing observability and deployment patterns<\/li>\n<li>Security teams rolling out network\/security appliances<\/li>\n<li>Application teams needing quick environments for PoCs and pilots<\/li>\n<li>Procurement\/FinOps teams aligning software spend with cloud consumption<\/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>Single VM appliances (common for network\/security tools)<\/li>\n<li>Web apps and CMS stacks (dev\/test and small production)<\/li>\n<li>Logging\/monitoring stacks (dev\/test or scaled-out production if designed properly)<\/li>\n<li>CI\/CD components (runners, artifact tools) depending on listing availability<\/li>\n<li>Kubernetes add-ons and platform tooling (verify packaging model per listing)<\/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>PoC environments<\/strong>: fast evaluation of products with minimal setup.<\/li>\n<li><strong>Dev\/test<\/strong>: repeatable environments aligned with production.<\/li>\n<li><strong>Production<\/strong>: when listings support HA, scaling, and operational best practices.<\/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>Dev\/test<\/strong>: prefer free\/BYOL listings, Always Free eligible shapes where possible, smaller footprints.<\/li>\n<li><strong>Production<\/strong>: require documented HA, patching\/upgrades, monitoring, backup\/DR, and clear support SLAs.<\/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 ways teams use Marketplace Guide in Oracle Cloud.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Deploy a security appliance into a hub VCN<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> You need centralized traffic inspection (north-south and\/or east-west).<\/li>\n<li><strong>Why Marketplace Guide fits:<\/strong> Many security vendors publish validated OCI images and reference patterns.<\/li>\n<li><strong>Example:<\/strong> A security team deploys a partner firewall image into a shared services VCN, integrates route tables, and funnels workload subnets through inspection.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Launch an observability stack for a new product team<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Teams need logs\/metrics\/traces quickly without long platform lead time.<\/li>\n<li><strong>Why it fits:<\/strong> Marketplace listings can provide deployable stacks with dependencies and defaults.<\/li>\n<li><strong>Example:<\/strong> A platform team deploys a monitoring stack into a tooling compartment and grants read-only access to app teams.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Standardize \u201cgolden\u201d base images for application VMs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Inconsistent VM builds create patching and security drift.<\/li>\n<li><strong>Why it fits:<\/strong> Marketplace images can provide maintained baselines (publisher-dependent).<\/li>\n<li><strong>Example:<\/strong> An ops team chooses a hardened OS image listing and mandates it via internal standards.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Accelerate migration by deploying compatible middleware components<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A legacy app depends on a specific middleware distribution.<\/li>\n<li><strong>Why it fits:<\/strong> Marketplace can offer vendor-supported images for middleware components.<\/li>\n<li><strong>Example:<\/strong> A migration team deploys a vendor\u2019s middleware VM image and connects it to OCI Database services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Rapid PoC of a commercial data tool (BYOL)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> You need to validate a tool before buying.<\/li>\n<li><strong>Why it fits:<\/strong> BYOL listings allow you to deploy quickly using an existing license.<\/li>\n<li><strong>Example:<\/strong> A data engineering team deploys a BYOL ETL tool into a sandbox region, tests with Object Storage, and tears it down.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Deploy a multi-tier application using Resource Manager stacks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Manual provisioning is slow and error-prone.<\/li>\n<li><strong>Why it fits:<\/strong> Terraform stacks can create VCN, subnets, instances, LB, and IAM in one flow.<\/li>\n<li><strong>Example:<\/strong> A developer deploys a sample 3-tier app stack to learn OCI networking patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Create a secure jump\/bastion pattern for operations access<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Admin access to private subnets must be controlled.<\/li>\n<li><strong>Why it fits:<\/strong> Some listings provide hardened bastion\/jump host setups (verify availability).<\/li>\n<li><strong>Example:<\/strong> An ops team deploys a hardened SSH bastion image and restricts access via NSGs and IAM.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Procurement-friendly deployment of licensed partner software<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> You need chargeback and licensing aligned with cloud billing.<\/li>\n<li><strong>Why it fits:<\/strong> Some Marketplace listings support metered billing integrated with OCI billing (verify per listing).<\/li>\n<li><strong>Example:<\/strong> Finance wants a single invoice approach; the team selects a listing with integrated billing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Deploy developer tools in isolated compartments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Tooling needs isolation from production workloads.<\/li>\n<li><strong>Why it fits:<\/strong> Compartment-scoped governance works well with Marketplace deployments.<\/li>\n<li><strong>Example:<\/strong> A DevOps team deploys a CI runner tool from Marketplace into a \u201cTooling\u201d compartment with tight IAM.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Build an internal catalog of \u201capproved\u201d solutions<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Teams deploy random software, increasing security and support risk.<\/li>\n<li><strong>Why it fits:<\/strong> Marketplace enables a curated approach: approved publishers\/listings + IAM restrictions.<\/li>\n<li><strong>Example:<\/strong> Platform engineering publishes internal guidance: \u201cUse only these Marketplace listings for X.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Disaster recovery and rebuild automation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Rebuilding critical tooling after an incident takes too long.<\/li>\n<li><strong>Why it fits:<\/strong> Versioned listings and IaC stacks support fast re-provisioning.<\/li>\n<li><strong>Example:<\/strong> An SRE team uses a Marketplace stack as part of DR runbooks to recreate a toolchain environment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Training and labs at low cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Students need real systems without spending days configuring.<\/li>\n<li><strong>Why it fits:<\/strong> Prebuilt images and stacks reduce setup time.<\/li>\n<li><strong>Example:<\/strong> An instructor uses a free Marketplace listing to teach VCN + Compute + security lists basics.<\/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<blockquote>\n<p>Note: Exact features depend on Oracle Cloud Marketplace\u2019s current implementation and on each listing. Verify in the official docs and in the specific listing you choose: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">1) Search and discovery across categories<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides filtering\/search for listings by type, publisher, and category.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces time spent evaluating solutions.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster selection of an image\/stack aligned with your workload.<\/li>\n<li><strong>Caveat:<\/strong> Results vary by region and tenancy; some listings may not be available everywhere.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Listing detail pages with documentation and support info<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Shows publisher docs, deployment instructions, and support contacts\/model.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents ambiguous ownership during incidents.<\/li>\n<li><strong>Practical benefit:<\/strong> You can establish operational responsibility before going live.<\/li>\n<li><strong>Caveat:<\/strong> Documentation quality varies by publisher.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Terms acceptance \/ subscription workflow<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Requires acceptance of license terms for many listings.<\/li>\n<li><strong>Why it matters:<\/strong> Legal compliance and billing correctness.<\/li>\n<li><strong>Practical benefit:<\/strong> A clear \u201cwho accepted what and when\u201d point (auditability depends on your governance).<\/li>\n<li><strong>Caveat:<\/strong> Acceptance may be tenancy-wide; coordinate with procurement\/security.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Image-based deployments (Compute instances from Marketplace images)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lets you launch a VM from a Marketplace-provided image.<\/li>\n<li><strong>Why it matters:<\/strong> Speeds up provisioning with preinstalled software.<\/li>\n<li><strong>Practical benefit:<\/strong> Fewer manual steps; consistent baseline.<\/li>\n<li><strong>Caveat:<\/strong> You still own patching, hardening, and network exposure unless the listing explicitly manages it.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Stack-based deployments (OCI Resource Manager \/ Terraform)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Deploys a set of OCI resources from a published stack.<\/li>\n<li><strong>Why it matters:<\/strong> Infrastructure-as-Code repeatability and safer changes.<\/li>\n<li><strong>Practical benefit:<\/strong> One workflow can create network, compute, load balancers, IAM artifacts, etc.<\/li>\n<li><strong>Caveat:<\/strong> Variable sets differ per stack; review before apply. Ensure least-privilege IAM for Resource Manager.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Versioning of listing artifacts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Many listings provide versions (image versions or stack versions).<\/li>\n<li><strong>Why it matters:<\/strong> Reproducibility and controlled upgrades.<\/li>\n<li><strong>Practical benefit:<\/strong> You can pin versions for stability and test upgrades in dev first.<\/li>\n<li><strong>Caveat:<\/strong> Publishers may deprecate versions; plan upgrade windows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Billing integration (where applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Some listings support billing through Oracle (metered) or BYOL; others are free.<\/li>\n<li><strong>Why it matters:<\/strong> Avoids surprise spend and procurement issues.<\/li>\n<li><strong>Practical benefit:<\/strong> Aligns consumption with cost tracking.<\/li>\n<li><strong>Caveat:<\/strong> Pricing models vary widely; always read the listing pricing section.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Publisher ecosystem and partner solutions<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Offers access to software from Oracle and third-party publishers.<\/li>\n<li><strong>Why it matters:<\/strong> Wider choice than building everything internally.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster adoption of security\/ops tools and enterprise software.<\/li>\n<li><strong>Caveat:<\/strong> Vendor lock-in can increase; plan exit strategies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Compartment-aware deployment targets<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Deployments can usually be targeted to specific compartments.<\/li>\n<li><strong>Why it matters:<\/strong> Enables multi-team governance boundaries.<\/li>\n<li><strong>Practical benefit:<\/strong> Isolation, billing separation, and policy enforcement.<\/li>\n<li><strong>Caveat:<\/strong> If IAM is too permissive, teams may deploy into the wrong compartments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Integration with OCI governance (Audit, IAM, tagging)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Marketplace activities and resulting resources can be governed via OCI IAM and monitored via Audit (verify your tenancy configuration).<\/li>\n<li><strong>Why it matters:<\/strong> Enterprise-grade accountability.<\/li>\n<li><strong>Practical benefit:<\/strong> You can investigate \u201cwho deployed what\u201d and apply tagging standards.<\/li>\n<li><strong>Caveat:<\/strong> Governance applies more strongly to the OCI resources created than to the Marketplace catalog itself; confirm audit coverage in your environment.<\/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 architecture<\/h3>\n\n\n\n<p>Marketplace Guide is the front door to:\n1. <strong>Discover<\/strong> a listing in Oracle Cloud Marketplace.\n2. <strong>Accept terms \/ subscribe<\/strong> (if required).\n3. <strong>Deploy<\/strong> via:\n   &#8211; <strong>Compute image<\/strong> (launch instance)\n   &#8211; <strong>Resource Manager stack<\/strong> (Terraform job)\n4. Manage resulting OCI resources as normal: networking, IAM, monitoring, backups, patching.<\/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>Control plane<\/strong>: OCI Console\/Marketplace handles listing selection, subscription, and deployment initiation.<\/li>\n<li><strong>Provisioning<\/strong>:<\/li>\n<li>Image flow: provisioning goes through OCI Compute to create an instance with a specific image.<\/li>\n<li>Stack flow: provisioning goes through OCI Resource Manager to execute Terraform and create resources.<\/li>\n<li><strong>Data plane<\/strong>: Your deployed workloads (instances, LBs, etc.) handle application traffic inside your VCN.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services<\/h3>\n\n\n\n<p>Common integrations include:\n&#8211; <strong>OCI Identity and Access Management (IAM)<\/strong>: controls who can subscribe\/deploy and where.\n&#8211; <strong>OCI Resource Manager<\/strong>: executes Terraform stacks.\n&#8211; <strong>OCI Compute<\/strong>: runs VM instances from Marketplace images.\n&#8211; <strong>OCI Networking (VCN, Subnets, NSGs, Security Lists)<\/strong>: connectivity and exposure control.\n&#8211; <strong>OCI Logging\/Audit\/Monitoring<\/strong>: operational telemetry and governance.\n&#8211; <strong>OCI Vault<\/strong>: secrets for deployed apps (recommended when stacks support it).\n&#8211; <strong>OCI Object Storage<\/strong>: frequently used by apps for backups\/artifacts (depends on listing).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Tenancy, compartments<\/li>\n<li>VCN\/subnet (created by you or by a stack)<\/li>\n<li>Compute instances and boot volumes<\/li>\n<li>Optional: Load Balancer, Bastion, NAT\/Service Gateway, WAF (architecture dependent)<\/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>Human users authenticate to OCI and are authorized by IAM policies.<\/li>\n<li>Resource Manager (if used) runs with permissions to create\/update\/delete resources (via policies).<\/li>\n<li>Deployed workloads authenticate to other OCI services using:<\/li>\n<li>Instance Principals \/ Dynamic Groups (recommended where supported)<\/li>\n<li>API keys or tokens (avoid if possible; use Vault)<\/li>\n<li>Service accounts within Kubernetes (for OKE-based designs)<\/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>Marketplace itself does not handle runtime traffic.<\/li>\n<li>Your design decides:<\/li>\n<li>public vs private subnets<\/li>\n<li>ingress\/egress controls<\/li>\n<li>whether to expose UI\/admin ports publicly (usually avoid)<\/li>\n<li>whether to use a load balancer\/WAF\/bastion<\/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>Enable and use:<\/li>\n<li><strong>OCI Audit<\/strong> for control-plane actions<\/li>\n<li><strong>OCI Logging<\/strong> for OS\/application logs (agent-based where needed)<\/li>\n<li><strong>OCI Monitoring<\/strong> for metrics and alarms (compute, LB, DB, etc.)<\/li>\n<li>Standardize:<\/li>\n<li>tagging (cost center, owner, environment)<\/li>\n<li>naming conventions<\/li>\n<li>patch cadence and golden image strategy<\/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  U[User \/ Engineer] --&gt;|Search &amp; Select| M[Oracle Cloud Marketplace&lt;br\/&gt;Marketplace Guide]\n  M --&gt;|Accept Terms \/ Subscribe| S[Marketplace Subscription]\n  M --&gt;|Deploy via Image| C[OCI Compute Instance]\n  M --&gt;|Deploy via Stack| RM[OCI Resource Manager (Terraform)]\n  RM --&gt; VCN[VCN\/Subnets\/NSGs]\n  RM --&gt; C\n  C --&gt; APP[Application Service]\n  APP --&gt;|Metrics\/Logs| OBS[Monitoring\/Logging]\n  C --&gt;|Audit Events| AUD[OCI Audit]\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (example pattern)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Tenancy[OCI Tenancy]\n    subgraph CompartmentShared[Compartment: Shared Services]\n      RM[Resource Manager Stack&lt;br\/&gt;(from Marketplace listing)]\n      VCN[VCN]\n      subgraph PublicSubnet[Public Subnet]\n        LB[Load Balancer]\n        NAT[NAT Gateway&lt;br\/&gt;(optional)]\n      end\n      subgraph PrivateSubnet[Private Subnet]\n        APP[App VM(s) from Marketplace Image]\n        DB[(Database Service or VM DB)]\n      end\n      WAF[WAF (optional)]\n      BAST[OCI Bastion (recommended)]\n      VAULT[OCI Vault]\n      LOG[Logging]\n      MON[Monitoring\/Alarms]\n      AUD[Audit]\n    end\n  end\n\n  Users[End Users] --&gt; WAF --&gt; LB --&gt; APP\n  Admins[Admins\/Operators] --&gt; BAST --&gt; APP\n  APP --&gt; DB\n  APP --&gt; VAULT\n  APP --&gt; LOG\n  APP --&gt; MON\n  RM --&gt; VCN\n  RM --&gt; APP\n  RM --&gt; LB\n  AUD --&gt; SecOps[Security\/Compliance Review]\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<h3 class=\"wp-block-heading\">Tenancy and account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>Oracle Cloud<\/strong> tenancy with permission to use OCI Console.<\/li>\n<li>Ability to create or use:<\/li>\n<li>Compartments<\/li>\n<li>Networking (VCN\/subnets\/NSGs\/security lists)<\/li>\n<li>Compute instances<\/li>\n<li>Resource Manager stacks (if your listing uses stacks)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>At minimum, the deploying user\/group typically needs:\n&#8211; Permissions to <strong>read\/subscribe<\/strong> to Marketplace listings\n&#8211; Permissions to <strong>create\/manage<\/strong> the resources the listing will deploy (Compute, VCN, etc.)<\/p>\n\n\n\n<p>OCI IAM policy resource names and verbs can vary by service and may change over time. For Marketplace-related policies, OCI historically used resource types like <code>app-catalog-listings<\/code> and <code>app-catalog-subscriptions<\/code> in some contexts. <strong>Verify the exact policy syntax in official IAM docs before applying<\/strong>.<\/p>\n\n\n\n<p>Start with least privilege:\n&#8211; Separate roles for:\n  &#8211; Marketplace browsing\/subscription\n  &#8211; Deployment execution (Resource Manager \/ Compute)\n  &#8211; Network administration<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A payment method or enterprise agreement may be required depending on listing pricing.<\/li>\n<li>Some listings are free but still create billable OCI resources (Compute, storage, load balancer, egress).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools (optional but recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access (required for most beginners).<\/li>\n<li>OCI CLI (optional for verification\/cleanup):<\/li>\n<li>https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/li>\n<li>SSH client for VM access (OpenSSH).<\/li>\n<li>Terraform knowledge if using Resource Manager stacks (Resource Manager abstracts some Terraform steps, but understanding helps).<\/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>Marketplace listings may be <strong>region-limited<\/strong>.<\/li>\n<li>Your tenancy must be subscribed to the target region, and the listing must support it. Always confirm in the listing.<\/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>Tenancy limits for:<\/li>\n<li>Compute instances \/ OCPUs<\/li>\n<li>Public IPs<\/li>\n<li>Block volumes<\/li>\n<li>Load balancers<\/li>\n<li>Resource Manager jobs\/concurrency (if applicable)<\/li>\n<li>Always check <strong>Service Limits<\/strong> in OCI Console for your region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VCN (existing or created by stack)<\/li>\n<li>IAM policies and groups<\/li>\n<li>Compute shapes available in your region (and Free Tier eligibility if you want low cost)<\/li>\n<\/ul>\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<p>Marketplace Guide (Oracle Cloud Marketplace) does not typically have a simple \u201cper hour\u201d price tag as a standalone service. Costs come from two places:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>OCI infrastructure resources created by the listing<\/strong>\n   &#8211; Compute hours, boot volumes, block volumes\n   &#8211; Load Balancer hours and bandwidth\n   &#8211; Network egress\n   &#8211; Database services, OKE clusters, etc.<\/p>\n<\/li>\n<li>\n<p><strong>Marketplace listing charges (publisher license)<\/strong>\n   &#8211; Some are <strong>free<\/strong>\n   &#8211; Some are <strong>BYOL<\/strong> (Bring Your Own License)\n   &#8211; Some are <strong>metered\/paid<\/strong> through Oracle billing or directly via publisher arrangements (depends on listing)<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions to watch<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Compute shape and hours<\/strong> (Always Free vs paid)<\/li>\n<li><strong>Storage<\/strong>:<\/li>\n<li>boot volume size<\/li>\n<li>block volume size and performance tier<\/li>\n<li><strong>Load balancer<\/strong>: can be a major cost driver for \u201csimple\u201d stacks<\/li>\n<li><strong>Network egress<\/strong>: especially for internet-facing apps, updates, and user traffic<\/li>\n<li><strong>High availability<\/strong>: multiple instances across ADs\/FDs doubles\/triples costs<\/li>\n<li><strong>License metrics<\/strong> (if paid): per OCPU, per instance, per user, per throughput, etc. (varies)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier (if applicable)<\/h3>\n\n\n\n<p>OCI has an <strong>Always Free<\/strong> tier for certain resources (availability and eligible shapes can change). If you want a low-cost Marketplace deployment:\n&#8211; Prefer listings that support <strong>Always Free eligible compute shapes<\/strong> and minimal extra services.\n&#8211; Verify current Always Free details in official docs\/pricing pages.<\/p>\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><strong>Support costs<\/strong> (publisher support subscriptions may be separate).<\/li>\n<li><strong>Operational tooling<\/strong>: logging retention, monitoring, SIEM export.<\/li>\n<li><strong>Backups<\/strong>: object storage and database backups.<\/li>\n<li><strong>Security services<\/strong>: WAF, vulnerability scanning, Bastion.<\/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>Ingress to OCI is typically free; <strong>egress<\/strong> to the internet is commonly charged (region-dependent).<\/li>\n<li>Traffic between regions can be charged.<\/li>\n<li>If your Marketplace deployment serves internet users, model egress carefully.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start in dev\/test with:<\/li>\n<li>Always Free shapes (where compatible)<\/li>\n<li>single-instance deployments<\/li>\n<li>minimal storage sizes<\/li>\n<li>no load balancer unless required<\/li>\n<li>Avoid leaving PoCs running\u2014automate teardown.<\/li>\n<li>For production:<\/li>\n<li>right-size shapes using monitoring<\/li>\n<li>use autoscaling where applicable (for app tiers)<\/li>\n<li>evaluate license models (BYOL vs metered)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (non-numeric)<\/h3>\n\n\n\n<p>A low-cost Marketplace proof-of-concept typically includes:\n&#8211; 1 small VM instance (Always Free eligible if supported)\n&#8211; 1 boot volume\n&#8211; 1 public IP\n&#8211; A VCN with a public subnet and security rules<\/p>\n\n\n\n<p>Total cost can be <strong>near-zero<\/strong> if all components fit Always Free and egress is minimal\u2014<strong>but verify eligibility and current limits<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations (non-numeric)<\/h3>\n\n\n\n<p>A production Marketplace-based deployment often adds:\n&#8211; Multiple VMs across fault domains\/availability domains\n&#8211; Load balancer + health checks\n&#8211; Private subnets, NAT, service gateways\n&#8211; WAF\n&#8211; Central logging, longer retention\n&#8211; Backups and DR copies\n&#8211; Paid licenses\/support from publisher<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing references<\/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>OCI price list: https:\/\/www.oracle.com\/cloud\/price-list\/<\/li>\n<li>OCI cost estimator (verify current URL\/availability): https:\/\/www.oracle.com\/cloud\/cost-estimator.html<\/li>\n<li>Marketplace listing pages include their own pricing\/licensing sections (review per listing).<\/li>\n<\/ul>\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 demonstrates a safe, beginner-friendly workflow that is realistic across many tenancies: <strong>subscribe to a free Marketplace listing and deploy it into a compartment<\/strong>, then verify and clean up.<\/p>\n\n\n\n<p>Because Marketplace inventory changes over time and differs by region\/tenancy, this tutorial uses <strong>decision points<\/strong> where you select an available <strong>Free<\/strong> listing (image or stack). The steps remain executable, but you must choose a listing that exists in your region.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use Oracle Cloud <strong>Marketplace Guide<\/strong> to:\n  1. Find a free Marketplace listing\n  2. Accept terms (subscribe)\n  3. Deploy the listing (preferably via a stack or VM image)\n  4. Validate the deployment\n  5. Clean up all resources to avoid cost<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n&#8211; Create (or choose) a compartment for the lab\n&#8211; Locate a free listing (preferably a simple web app\/demo stack or utility VM image)\n&#8211; Deploy into a new or existing VCN\n&#8211; Validate via public IP \/ console checks\n&#8211; Terminate resources and delete related networking (if created solely for the lab)<\/p>\n\n\n\n<blockquote>\n<p>Cost control tip: If you want the lowest cost, aim for an <strong>Always Free eligible compute shape<\/strong> and avoid listings that create a <strong>Load Balancer<\/strong> or multiple instances.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare a compartment and tags (governance first)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In OCI Console, open the navigation menu \u2192 <strong>Identity &amp; Security<\/strong> \u2192 <strong>Compartments<\/strong>.<\/li>\n<li>Click <strong>Create Compartment<\/strong>.<\/li>\n<li>Name it: <code>cmp-marketplace-lab<\/code> (example)<\/li>\n<li>(Optional) Add a description and tags such as:\n   &#8211; <code>Environment=Lab<\/code>\n   &#8211; <code>Owner=&lt;your-name-or-team&gt;<\/code>\n   &#8211; <code>CostCenter=Training<\/code><\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A dedicated compartment exists to keep lab resources isolated.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; You can see <code>cmp-marketplace-lab<\/code> in the compartment list.\n&#8211; You can select it from the compartment picker.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Confirm you have permissions (IAM)<\/h3>\n\n\n\n<p>You need permission to:\n&#8211; Browse\/subscribe to Marketplace listings\n&#8211; Create resources (at least Compute + Networking; and Resource Manager if using stacks)<\/p>\n\n\n\n<p>If you are not an admin, ask your tenancy admin to grant you the minimum required policies. Because policy statements vary based on what you deploy, use this approach:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For <strong>Compute + Networking<\/strong> deployments:<\/li>\n<li>Allow group to manage instances and VCN resources in the lab compartment.<\/li>\n<li>For <strong>Resource Manager<\/strong> stack deployments:<\/li>\n<li>Allow group to manage Resource Manager stacks\/jobs and the underlying resources.<\/li>\n<\/ul>\n\n\n\n<blockquote>\n<p>Verify exact OCI IAM policy syntax in official docs before applying. Start here and navigate to IAM policy reference: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can create resources in <code>cmp-marketplace-lab<\/code> and can proceed to Marketplace without authorization errors.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; You can open Marketplace listings.\n&#8211; You can start a deployment workflow and select your compartment.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Find a Free Marketplace listing appropriate for a lab<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the navigation menu \u2192 <strong>Marketplace<\/strong>.<\/li>\n<li>In Marketplace:\n   &#8211; Filter for <strong>Free<\/strong> (if the filter exists in your UI), or search for keywords like:<ul>\n<li><code>NGINX<\/code><\/li>\n<li><code>WordPress<\/code><\/li>\n<li><code>Open Source<\/code><\/li>\n<li><code>Free<\/code><\/li>\n<li><code>Terraform<\/code><\/li>\n<\/ul>\n<\/li>\n<li>Open a candidate listing and confirm:\n   &#8211; It supports your <strong>region<\/strong>\n   &#8211; It is <strong>Free<\/strong> or <strong>BYOL<\/strong> (avoid metered paid listings for a first lab)\n   &#8211; Deployment type:<ul>\n<li><strong>Image<\/strong> (VM image) or<\/li>\n<li><strong>Stack<\/strong> (Resource Manager\/Terraform)<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have selected one free listing that you can deploy in your region.<\/p>\n\n\n\n<p><strong>Verification checklist (on the listing page):<\/strong>\n&#8211; Pricing\/licensing: free\/BYOL confirmed\n&#8211; Supported regions: includes your region\n&#8211; Deployment instructions: clear enough for a lab\n&#8211; Network exposure: you understand what ports it will open (especially if it\u2019s a web app)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Subscribe \/ accept terms for the listing<\/h3>\n\n\n\n<p>Most listings require you to accept terms before deployment.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>On the listing page, click <strong>Get App<\/strong> \/ <strong>Subscribe<\/strong> \/ <strong>Accept Terms<\/strong> (button text varies).<\/li>\n<li>Read:\n   &#8211; License terms\n   &#8211; Support statement\n   &#8211; Any data collection notes (if stated)<\/li>\n<li>Accept terms and confirm the subscription.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Your tenancy is subscribed to the listing and allowed to deploy it.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; The listing shows as \u201cSubscribed\u201d or similar status.\n&#8211; If there is a \u201cMy Subscriptions\u201d section in Marketplace, confirm it appears there (UI varies).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5 (Option A): Deploy using a Marketplace Stack (Resource Manager)<\/h3>\n\n\n\n<p>Choose this option if the listing deploys via a stack.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>On the listing, choose <strong>Launch Stack<\/strong> (or equivalent).<\/li>\n<li>In the <strong>Create Stack<\/strong> page:\n   &#8211; Select <strong>Compartment<\/strong>: <code>cmp-marketplace-lab<\/code>\n   &#8211; Set a stack name, e.g., <code>stk-marketplace-lab<\/code>\n   &#8211; Review the Terraform version (if shown)<\/li>\n<li>On the <strong>Configure Variables<\/strong> page:\n   &#8211; Read every variable description carefully.\n   &#8211; Choose cost-minimizing options when available:<ul>\n<li>smallest shape supported (prefer Always Free eligible shapes if supported)<\/li>\n<li>single instance<\/li>\n<li>minimal storage sizes<\/li>\n<li>Provide SSH public key if required (many stacks require it).<\/li>\n<\/ul>\n<\/li>\n<li>Create the stack.<\/li>\n<li>Run <strong>Plan<\/strong> (if available) and review what will be created.<\/li>\n<li>Run <strong>Apply<\/strong> to deploy.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Resource Manager creates the required OCI resources (VCN\/Compute\/etc.).<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; In Resource Manager, the job status becomes <strong>Succeeded<\/strong>.\n&#8211; The outputs section (if provided) includes useful values like:\n  &#8211; public IP\n  &#8211; URL\n  &#8211; instance OCID<\/p>\n\n\n\n<blockquote>\n<p>If the stack creates a load balancer and you didn\u2019t intend to pay for it, stop and destroy immediately.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5 (Option B): Deploy using a Marketplace Image (Compute instance)<\/h3>\n\n\n\n<p>Choose this option if the listing is an image-based app.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>From the listing, click <strong>Launch Instance<\/strong> (or follow the listing\u2019s deployment path to Compute).<\/li>\n<li>In <strong>Create Compute Instance<\/strong>:\n   &#8211; Name: <code>vm-marketplace-lab<\/code>\n   &#8211; Compartment: <code>cmp-marketplace-lab<\/code>\n   &#8211; Image: choose the Marketplace image\/version\n   &#8211; Shape: choose a small shape (prefer Always Free eligible if supported)<\/li>\n<li>Networking:\n   &#8211; Create a <strong>new VCN<\/strong> for lab (or select an existing lab VCN)\n   &#8211; Place instance in a <strong>public subnet<\/strong> if you need direct web access<\/li>\n<li>Add your <strong>SSH public key<\/strong><\/li>\n<li>Review \u201cAdvanced options\u201d only if the listing requires it.<\/li>\n<li>Click <strong>Create<\/strong>.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A VM instance launches using the Marketplace image.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Instance state becomes <strong>Running<\/strong>\n&#8211; The instance has a <strong>public IP<\/strong> if you selected a public subnet and enabled public IP assignment<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Validate functionality<\/h3>\n\n\n\n<p>Validation depends on what you deployed. Use these common checks:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">A) Confirm OCI resources exist<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In <code>cmp-marketplace-lab<\/code>, check:<\/li>\n<li><strong>Compute<\/strong> \u2192 Instances<\/li>\n<li><strong>Networking<\/strong> \u2192 VCN, Subnets, Security Lists\/NSGs<\/li>\n<li><strong>Resource Manager<\/strong> \u2192 Stack and Job details (if stack-based)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">B) If it\u2019s a web app, test HTTP\/HTTPS access<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Locate the public IP (instance public IP or load balancer IP).<\/li>\n<li>Test from your machine:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">curl -I http:\/\/&lt;PUBLIC_IP_OR_DNS_NAME&gt;\n<\/code><\/pre>\n\n\n\n<p>If HTTPS is configured:<\/p>\n\n\n\n<pre><code class=\"language-bash\">curl -I https:\/\/&lt;PUBLIC_IP_OR_DNS_NAME&gt;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> You receive an HTTP response (200\/301\/302 are common). If you get timeout, check security rules.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">C) SSH access (if enabled)<\/h4>\n\n\n\n<pre><code class=\"language-bash\">ssh -i \/path\/to\/private_key opc@&lt;PUBLIC_IP&gt;\n<\/code><\/pre>\n\n\n\n<p>Usernames differ by image (Oracle Linux commonly uses <code>opc<\/code>). <strong>Verify in listing docs<\/strong>.<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can log in and see the deployed software\/services.<\/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:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[ ] You successfully subscribed\/accepted terms to the listing<\/li>\n<li>[ ] Deployment completed (instance running or stack job succeeded)<\/li>\n<li>[ ] You can reach the service (web page, API response, or SSH)<\/li>\n<li>[ ] You identified all created resources (for cleanup and cost control)<\/li>\n<li>[ ] You captured outputs (public IPs, URLs, credentials locations)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">1) \u201cNot authorized\u201d \/ \u201cForbidden\u201d when deploying<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cause:<\/strong> Missing IAM permissions in the target compartment.<\/li>\n<li><strong>Fix:<\/strong> Ask admin to grant least-privilege policies for:<\/li>\n<li>compute instances<\/li>\n<li>vcn\/subnets\/security rules<\/li>\n<li>resource manager stacks\/jobs (if applicable)<\/li>\n<li>marketplace subscription actions (verify policy resource types in docs)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">2) Listing not available in your region<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cause:<\/strong> Publisher restricts regions.<\/li>\n<li><strong>Fix:<\/strong> Choose another listing, or deploy in a region where it is available (if your tenancy is subscribed to that region).<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">3) Stack apply fails (Terraform errors)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cause:<\/strong> Quota limits, naming conflicts, unsupported shapes, missing variables.<\/li>\n<li><strong>Fix:<\/strong><\/li>\n<li>Read the job logs carefully.<\/li>\n<li>Reduce size\/footprint.<\/li>\n<li>Ensure required variables are set (SSH key, compartment, network selections).<\/li>\n<li>Check service limits for compute\/public IP\/LB.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">4) Can\u2019t access the web app (timeout)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cause:<\/strong> Ingress rules not open, wrong subnet type, no public IP, NSG blocks traffic.<\/li>\n<li><strong>Fix:<\/strong><\/li>\n<li>Confirm instance has a public IP (or use LB).<\/li>\n<li>Confirm Security List\/NSG allows inbound TCP 80\/443 from your IP.<\/li>\n<li>Confirm route table and internet gateway exist for the public subnet.<\/li>\n<li>Check OS firewall (iptables\/firewalld) on the instance.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">5) SSH fails<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cause:<\/strong> Wrong username, blocked port 22, wrong key, no public IP.<\/li>\n<li><strong>Fix:<\/strong><\/li>\n<li>Verify username in listing docs.<\/li>\n<li>Ensure inbound TCP 22 allowed from your IP.<\/li>\n<li>Confirm correct private key used and permissions (<code>chmod 600<\/code>).<\/li>\n<li>Use OCI Console <strong>Instance Console Connection<\/strong> as a last resort (advanced).<\/li>\n<\/ul>\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 charges, delete everything created.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">If deployed via Resource Manager stack<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Resource Manager<\/strong> \u2192 Stacks \u2192 your stack.<\/li>\n<li>Run <strong>Destroy<\/strong> (or \u201cTerminate\u201d\/\u201cDestroy job\u201d depending on UI).<\/li>\n<li>Wait for job success.<\/li>\n<li>Verify resources are gone in the compartment.<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\">If deployed via Compute instance directly<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Compute<\/strong> \u2192 Instances \u2192 <code>vm-marketplace-lab<\/code> \u2192 <strong>Terminate<\/strong>\n   &#8211; Choose <strong>Permanently delete<\/strong> boot volume if you do not need it.<\/li>\n<li>Delete any additional block volumes created.<\/li>\n<li>If you created a VCN only for the lab:\n   &#8211; Delete dependent resources (LB, gateways, route tables attachments) if any\n   &#8211; Delete subnets\n   &#8211; Delete VCN<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected cleanup outcome:<\/strong> Compartment <code>cmp-marketplace-lab<\/code> contains no running instances, load balancers, or unattached volumes.<\/p>\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>Prefer <strong>stack-based deployments<\/strong> for repeatability and drift control (when well-authored).<\/li>\n<li>For production:<\/li>\n<li>Put workloads in <strong>private subnets<\/strong>.<\/li>\n<li>Use <strong>Load Balancer<\/strong> + <strong>WAF<\/strong> for public apps where appropriate.<\/li>\n<li>Use <strong>Bastion<\/strong> for admin access instead of public SSH.<\/li>\n<li>Design for failure:<\/li>\n<li>multi-instance tiers where needed<\/li>\n<li>backups and restore testing<\/li>\n<li>health checks and alarms<\/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>Enforce <strong>least privilege<\/strong>:<\/li>\n<li>Separate \u201cMarketplace subscription\u201d from \u201cdeployment execution\u201d roles.<\/li>\n<li>Restrict who can deploy into production compartments.<\/li>\n<li>Use <strong>dynamic groups + instance principals<\/strong> for OCI API access from instances (when applicable).<\/li>\n<li>Require <strong>MFA<\/strong> and strong identity controls for human users.<\/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>Treat Marketplace PoCs as <strong>ephemeral<\/strong>:<\/li>\n<li>tag resources<\/li>\n<li>set budget alerts<\/li>\n<li>schedule teardown<\/li>\n<li>Be cautious with stacks that create:<\/li>\n<li>load balancers<\/li>\n<li>multiple instances<\/li>\n<li>large block volumes<\/li>\n<li>Prefer Always Free eligible resources for training (verify current eligibility).<\/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 assume marketplace defaults are right for your workload.<\/li>\n<li>Right-size shapes using monitoring data.<\/li>\n<li>Use OCI Load Balancer and caching patterns where appropriate.<\/li>\n<li>Validate storage performance tiers if the app is I\/O sensitive.<\/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>Avoid single points of failure for production.<\/li>\n<li>Use multiple fault domains\/ADs where the region supports it.<\/li>\n<li>Automate rebuilds (IaC) and document runbooks.<\/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>Standardize:<\/li>\n<li>patching process (OS and application)<\/li>\n<li>log collection and retention<\/li>\n<li>vulnerability scanning (where applicable)<\/li>\n<li>Use alarms:<\/li>\n<li>CPU\/memory\/disk (agent-based for memory\/disk)<\/li>\n<li>instance down<\/li>\n<li>LB unhealthy backends<\/li>\n<li>Track ownership with tags and clear on-call rotations.<\/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>Tags to enforce:<\/li>\n<li><code>Owner<\/code><\/li>\n<li><code>Environment<\/code> (dev\/test\/prod)<\/li>\n<li><code>CostCenter<\/code><\/li>\n<li><code>DataSensitivity<\/code><\/li>\n<li>Naming:<\/li>\n<li>include app, environment, region, and tier (e.g., <code>app1-prod-web-01<\/code>)<\/li>\n<li>Maintain an internal \u201capproved listings\u201d register:<\/li>\n<li>listing name\/version<\/li>\n<li>publisher<\/li>\n<li>security review date<\/li>\n<li>support contact<\/li>\n<li>allowed compartments<\/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>Access to Marketplace and deployment actions is governed by <strong>OCI IAM<\/strong>.<\/li>\n<li>Apply compartment boundaries:<\/li>\n<li>Only platform\/security teams can deploy into shared or prod compartments.<\/li>\n<li>Developers deploy into dev\/test compartments only.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI encrypts many storage services at rest by default (service-dependent).<\/li>\n<li>For marketplace deployments:<\/li>\n<li>Ensure block volumes and boot volumes meet your encryption requirements (default encryption is typical).<\/li>\n<li>Use customer-managed keys (Vault) if policy requires (verify service support).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<p>Common risk: Marketplace listings that deploy a web UI\/admin interface directly to the public internet.\n&#8211; Prefer:\n  &#8211; private subnet deployment\n  &#8211; access via Bastion\/VPN\/FastConnect\n  &#8211; restrict ingress to corporate IPs\n&#8211; Use NSGs for tighter, instance-level control.\n&#8211; Avoid \u201c0.0.0.0\/0\u201d on admin ports.<\/p>\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 store secrets in:<\/li>\n<li>instance user-data<\/li>\n<li>Terraform variables in plaintext<\/li>\n<li>images<\/li>\n<li>Prefer <strong>OCI Vault<\/strong> for secrets; integrate apps to fetch secrets at runtime when possible.<\/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>Enable and review <strong>OCI Audit<\/strong> events for:<\/li>\n<li>subscription acceptance<\/li>\n<li>instance creation\/termination<\/li>\n<li>network changes<\/li>\n<li>Centralize logs:<\/li>\n<li>OS logs via agent<\/li>\n<li>application logs as needed<\/li>\n<li>Ensure retention meets compliance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<p>Marketplace does not automatically make a deployment compliant.\n&#8211; You still need:\n  &#8211; asset inventory\n  &#8211; vulnerability management\n  &#8211; patch SLAs\n  &#8211; access reviews\n  &#8211; data residency checks (region)\n&#8211; If the listing includes telemetry\/phone-home behavior, review publisher docs and legal terms.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deploying production services into a public subnet with open ingress.<\/li>\n<li>Using default passwords from docs and never rotating.<\/li>\n<li>Over-permissive IAM policies for Resource Manager and users.<\/li>\n<li>Not understanding responsibility split: infrastructure vs software support.<\/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>Run a lightweight security review before production:<\/li>\n<li>ports exposed<\/li>\n<li>IAM access paths<\/li>\n<li>required OS hardening steps<\/li>\n<li>backup strategy<\/li>\n<li>Use a staging environment to validate:<\/li>\n<li>upgrades<\/li>\n<li>scaling behavior<\/li>\n<li>failover behavior<\/li>\n<li>Keep an exit plan: how to migrate off the marketplace listing if needed.<\/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<ul class=\"wp-block-list\">\n<li><strong>Listing availability varies by region<\/strong>: you may not find the same listing everywhere.<\/li>\n<li><strong>Publisher quality varies<\/strong>:<\/li>\n<li>documentation can be incomplete<\/li>\n<li>upgrade procedures may be unclear<\/li>\n<li><strong>Stacks may create expensive resources<\/strong> (especially load balancers and large storage) without obvious warnings\u2014review the plan carefully.<\/li>\n<li><strong>Support boundaries<\/strong> can be confusing:<\/li>\n<li>Oracle supports OCI infrastructure<\/li>\n<li>publisher supports the software (often)<\/li>\n<li>you support integration and operations unless contracted otherwise<\/li>\n<li><strong>IAM policy complexity<\/strong>: deploying stacks often needs broad permissions; constrain by compartment and separate duties.<\/li>\n<li><strong>Quotas\/service limits<\/strong>: PoC failures are frequently caused by public IP limits, instance limits, or shape availability.<\/li>\n<li><strong>Image update cadence<\/strong>: a marketplace image may lag behind security patches\u2014validate patch status.<\/li>\n<li><strong>Network assumptions<\/strong>: stacks may assume:<\/li>\n<li>public subnet access<\/li>\n<li>open ports<\/li>\n<li>specific CIDRs<\/li>\n<li><strong>Data egress surprises<\/strong>: internet-facing apps can generate meaningful egress costs.<\/li>\n<li><strong>Migration challenges<\/strong>:<\/li>\n<li>moving from a marketplace single VM to an HA architecture may require re-platforming<\/li>\n<li>BYOL licensing portability may require vendor confirmation<\/li>\n<\/ul>\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>Marketplace Guide is a \u201csolution acquisition + deployment accelerator.\u201d Alternatives include other cloud marketplaces, OCI-native building blocks, and self-managed internal catalogs.<\/p>\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 Marketplace (Marketplace Guide)<\/strong><\/td>\n<td>Deploying partner\/Oracle solutions on OCI quickly<\/td>\n<td>Integrated with OCI, listing-based procurement, images\/stacks accelerate deployment<\/td>\n<td>Listing availability varies by region; publisher quality varies; licensing can be complex<\/td>\n<td>You want fast, governed deployments on Oracle Cloud<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Resource Manager (without Marketplace)<\/strong><\/td>\n<td>Your own Terraform modules\/stacks<\/td>\n<td>Full control, internal standards, repeatable IaC<\/td>\n<td>You must author\/maintain modules and docs<\/td>\n<td>You already have mature IaC and want a paved road without third-party packaging<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Custom Images \/ Golden Images<\/strong><\/td>\n<td>Standardized VM baselines<\/td>\n<td>Strong internal control, consistent patching\/hardening<\/td>\n<td>Requires image pipeline and maintenance<\/td>\n<td>You must meet strict compliance and want full control<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Marketplace<\/strong><\/td>\n<td>Similar needs on AWS<\/td>\n<td>Large ecosystem; mature procurement patterns<\/td>\n<td>Not OCI; different IAM\/network model<\/td>\n<td>Your workloads primarily run on AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Marketplace<\/strong><\/td>\n<td>Similar needs on Azure<\/td>\n<td>Strong enterprise procurement integrations<\/td>\n<td>Not OCI; different deployment models<\/td>\n<td>You\u2019re standardized on Azure<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Marketplace<\/strong><\/td>\n<td>Similar needs on GCP<\/td>\n<td>Integrated deployments and billing options<\/td>\n<td>Not OCI; ecosystem differs<\/td>\n<td>You\u2019re standardized on GCP<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed internal catalog (e.g., Backstage + Terraform modules)<\/strong><\/td>\n<td>Large enterprises with strict governance<\/td>\n<td>Maximum governance and standardization<\/td>\n<td>Higher engineering effort; slower onboarding<\/td>\n<td>You need deep control and internal approval workflows<\/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: Centralized security inspection using a partner appliance listing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A regulated enterprise needs standardized inbound\/outbound traffic inspection and segmentation across multiple application teams on Oracle Cloud.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Use Marketplace Guide to select an approved partner security appliance listing.<\/li>\n<li>Deploy via stack into a <strong>Shared Services<\/strong> compartment.<\/li>\n<li>Hub-and-spoke VCN pattern:<ul>\n<li>Hub VCN hosts the inspection layer<\/li>\n<li>Spoke VCNs host applications<\/li>\n<li>Routing directs traffic through the inspection tier<\/li>\n<\/ul>\n<\/li>\n<li>Integrate with:<ul>\n<li>OCI Audit for governance<\/li>\n<li>Central Logging for security logs<\/li>\n<li>Vault for secrets (where supported)<\/li>\n<\/ul>\n<\/li>\n<li><strong>Why this service was chosen:<\/strong><\/li>\n<li>Faster deployment than manual image building.<\/li>\n<li>Easier standardization: one approved listing\/version and repeatable deployment.<\/li>\n<li>Procurement alignment via listing licensing terms.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Reduced time to deploy inspection controls.<\/li>\n<li>Consistent security posture across teams.<\/li>\n<li>Clear responsibility split between OCI operations and vendor appliance support.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: Quick deployment of a free web stack for a pilot<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A startup needs a working demo environment in Oracle Cloud for a customer pilot, but doesn\u2019t have time to build everything from scratch.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Use Marketplace Guide to deploy a free\/open-source app stack (image or Resource Manager stack).<\/li>\n<li>Deploy in a single compartment with strict tagging and budget alerts.<\/li>\n<li>Public endpoint with restricted admin access (Bastion or IP allowlist).<\/li>\n<li><strong>Why this service was chosen:<\/strong><\/li>\n<li>Rapid deployment and minimal setup time.<\/li>\n<li>Lower operational overhead for a short-lived pilot.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>A demo environment available in hours rather than days.<\/li>\n<li>Clear teardown path to avoid ongoing costs.<\/li>\n<li>A starting point to evolve into a more robust architecture if the pilot succeeds.<\/li>\n<\/ul>\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 Marketplace Guide a separate Oracle Cloud service?<\/strong><br\/>\nMarketplace Guide is best understood as guidance for using <strong>Oracle Cloud Marketplace<\/strong> rather than a distinct billable service. Verify naming in the official Marketplace docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/p>\n\n\n\n<p>2) <strong>Do Marketplace listings run \u201cinside\u201d Marketplace?<\/strong><br\/>\nNo. Marketplace is a catalog\/procurement layer. The actual software runs on OCI services (Compute, VCN, Resource Manager, etc.).<\/p>\n\n\n\n<p>3) <strong>Do I always need to \u201csubscribe\u201d before deploying?<\/strong><br\/>\nOften yes\u2014especially for licensed or partner solutions. Some free items may still require terms acceptance.<\/p>\n\n\n\n<p>4) <strong>Can I deploy Marketplace solutions into a private subnet only?<\/strong><br\/>\nUsually yes, but it depends on the listing\/stack. Review the architecture and variables. Some stacks assume public access unless you modify them.<\/p>\n\n\n\n<p>5) <strong>Who supports a Marketplace solution? Oracle or the publisher?<\/strong><br\/>\nUsually the <strong>publisher supports the software<\/strong>, and Oracle supports the <strong>OCI infrastructure<\/strong>. The listing should state the support model\u2014confirm before production.<\/p>\n\n\n\n<p>6) <strong>How do I avoid surprise costs?<\/strong><br\/>\nUse tags, budgets, and review the stack plan. Avoid stacks that create load balancers or multiple instances during PoC unless required.<\/p>\n\n\n\n<p>7) <strong>Are Marketplace images automatically patched?<\/strong><br\/>\nNot necessarily. After deployment, you typically own OS and application patching unless the publisher provides an automated update mechanism.<\/p>\n\n\n\n<p>8) <strong>Can I use OCI Always Free with Marketplace listings?<\/strong><br\/>\nSometimes\u2014if the listing supports Always Free eligible shapes and minimal extra services. Always Free eligibility changes over time; verify current requirements.<\/p>\n\n\n\n<p>9) <strong>Can I automate Marketplace deployments?<\/strong><br\/>\nCommonly, yes indirectly:\n&#8211; If the listing provides a Resource Manager stack, you can automate stack jobs.\n&#8211; For image-based deployments, you can automate instance creation using OCI APIs\/CLI once you have the right image and subscription terms accepted. Verify capabilities in official docs and your tenancy.<\/p>\n\n\n\n<p>10) <strong>Can I restrict which Marketplace listings teams can use?<\/strong><br\/>\nYou can restrict <strong>who can deploy<\/strong> and <strong>where<\/strong> via IAM compartments and policies. Catalog-level allow\/deny controls may be limited\u2014verify current governance features in official docs.<\/p>\n\n\n\n<p>11) <strong>What\u2019s the safest way to evaluate a new listing?<\/strong><br\/>\nDeploy into an isolated compartment and VCN, restrict ingress, and monitor network egress. Treat it like untrusted software until reviewed.<\/p>\n\n\n\n<p>12) <strong>Can Marketplace create IAM policies automatically via stacks?<\/strong><br\/>\nSome stacks can create IAM resources if permitted, but this is high risk. Prefer pre-created IAM policies with least privilege and avoid stacks that require tenancy-wide IAM permissions unless reviewed.<\/p>\n\n\n\n<p>13) <strong>How do I handle secrets created by a stack (passwords\/keys)?<\/strong><br\/>\nPrefer stacks that integrate with Vault or prompt you to supply secrets securely. If the stack outputs secrets in plaintext, treat outputs as sensitive and rotate immediately.<\/p>\n\n\n\n<p>14) <strong>What happens if a listing is removed or deprecated?<\/strong><br\/>\nYou can typically keep running deployed resources, but you may lose easy redeploy\/upgrade paths. Pin versions and maintain your own backup plan.<\/p>\n\n\n\n<p>15) <strong>Is Oracle Cloud Marketplace the same as AWS\/Azure marketplaces?<\/strong><br\/>\nConceptually similar (catalog + deployment + billing), but implementation, governance model, and listing availability differ.<\/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 Marketplace Guide<\/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 Marketplace docs<\/td>\n<td>Primary reference for Marketplace workflows and concepts. https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Identity and Access Management docs<\/td>\n<td>Required to implement least-privilege access for Marketplace deployments. https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/home.htm<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Resource Manager docs<\/td>\n<td>Essential if you deploy Marketplace stacks (Terraform). https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/ResourceManager\/home.htm<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Pricing<\/td>\n<td>Understand OCI resource costs that Marketplace deployments create. https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>OCI Price List<\/td>\n<td>Detailed SKU pricing reference (region\/service dependent). https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<\/tr>\n<tr>\n<td>Official tool<\/td>\n<td>OCI Cost Estimator<\/td>\n<td>Model costs for compute\/LB\/storage created by listings (verify current estimator availability). https:\/\/www.oracle.com\/cloud\/cost-estimator.html<\/td>\n<\/tr>\n<tr>\n<td>Official architecture<\/td>\n<td>Oracle Cloud Architecture Center<\/td>\n<td>Reference architectures relevant to apps you may deploy from Marketplace. https:\/\/www.oracle.com\/cloud\/architecture-center\/<\/td>\n<\/tr>\n<tr>\n<td>Official solutions<\/td>\n<td>Oracle Solutions on docs.oracle.com<\/td>\n<td>Step-by-step solution guides (some align with Marketplace-style deployments). https:\/\/docs.oracle.com\/en\/solutions\/<\/td>\n<\/tr>\n<tr>\n<td>Official training<\/td>\n<td>Oracle Cloud \u201cLearn\u201d content<\/td>\n<td>Tutorials and labs across OCI services you\u2019ll use with Marketplace. https:\/\/docs.oracle.com\/en\/learn\/<\/td>\n<\/tr>\n<tr>\n<td>Official CLI docs<\/td>\n<td>OCI CLI documentation<\/td>\n<td>Helpful for verification and cleanup automation. https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/td>\n<\/tr>\n<tr>\n<td>GitHub (Oracle)<\/td>\n<td>oracle\/terraform-provider-oci<\/td>\n<td>Useful background for Terraform\/Resource Manager behavior. https:\/\/github.com\/oracle\/terraform-provider-oci<\/td>\n<\/tr>\n<tr>\n<td>GitHub (Oracle)<\/td>\n<td>oracle-quickstart repositories (verify current org\/repo)<\/td>\n<td>Many OCI reference deployments and stacks live in Oracle GitHub orgs; validate relevance to your listing. https:\/\/github.com\/oracle<\/td>\n<\/tr>\n<tr>\n<td>Community (reputable)<\/td>\n<td>OCI blog and architecture posts (verify)<\/td>\n<td>Practical patterns and announcements; cross-check with docs. https:\/\/blogs.oracle.com\/cloud-infrastructure\/<\/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 training providers may offer Oracle Cloud and Marketplace-related learning. Verify course outlines, instructors, and recency directly on their websites.<\/p>\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, beginners to intermediate<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> DevOps practices, cloud operations fundamentals, automation concepts that complement OCI Marketplace deployments<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>ScmGalaxy.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> DevOps practitioners, build\/release engineers, students<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> SCM\/CI\/CD fundamentals that pair with deploying tooling from Marketplace<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website:<\/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 teams, platform teams<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> CloudOps and operational practices relevant after deploying Marketplace solutions<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/cloudopsnow.in\/<\/p>\n<\/li>\n<li>\n<p><strong>SreSchool.com<\/strong><br\/>\n   &#8211; <strong>Suitable audience:<\/strong> SREs, operations engineers, platform engineers<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> Reliability engineering practices (monitoring, incident response) for Marketplace-deployed workloads<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website:<\/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, monitoring\/observability practitioners<br\/>\n   &#8211; <strong>Likely learning focus:<\/strong> Observability and automation practices that apply to managing Marketplace solutions<br\/>\n   &#8211; <strong>Mode:<\/strong> Check website<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/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 appear to provide trainer information, training services, or related resources. Verify specialization and offerings directly.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>RajeshKumar.xyz<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> Cloud\/DevOps training and guidance (verify on site)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Beginners to intermediate practitioners<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/rajeshkumar.xyz\/<\/p>\n<\/li>\n<li>\n<p><strong>devopstrainer.in<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps training, CI\/CD, automation concepts<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> DevOps engineers, students, working professionals<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/devopstrainer.in\/<\/p>\n<\/li>\n<li>\n<p><strong>devopsfreelancer.com<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> Freelance DevOps support\/training resources (verify on site)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Teams needing short-term guidance or hands-on help<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/devopsfreelancer.com\/<\/p>\n<\/li>\n<li>\n<p><strong>devopssupport.in<\/strong><br\/>\n   &#8211; <strong>Likely specialization:<\/strong> DevOps support services and possibly training (verify on site)<br\/>\n   &#8211; <strong>Suitable audience:<\/strong> Operations\/DevOps teams needing implementation support<br\/>\n   &#8211; <strong>Website:<\/strong> https:\/\/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>These companies may offer consulting services related to cloud\/DevOps and could help with Oracle Cloud Marketplace deployments. Verify capabilities, references, and scope directly.<\/p>\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 on site)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> Architecture reviews, cloud migrations, operational readiness for Marketplace-based deployments<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> <\/p>\n<ul>\n<li>Reviewing a Marketplace stack for security and cost risks before production  <\/li>\n<li>Designing VCN\/subnet patterns for Marketplace-deployed tools  <\/li>\n<li><strong>Website:<\/strong> https:\/\/cotocus.com\/<\/li>\n<\/ul>\n<\/li>\n<li>\n<p><strong>DevOpsSchool.com<\/strong><br\/>\n   &#8211; <strong>Likely service area:<\/strong> DevOps consulting and training services (verify on site)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> CI\/CD, automation, operational best practices for workloads deployed from Marketplace<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> <\/p>\n<ul>\n<li>Implementing monitoring and incident response for Marketplace-deployed apps  <\/li>\n<li>Standardizing deployment pipelines around Terraform\/Resource Manager  <\/li>\n<li><strong>Website:<\/strong> https:\/\/www.devopsschool.com\/<\/li>\n<\/ul>\n<\/li>\n<li>\n<p><strong>DEVOPSCONSULTING.IN<\/strong><br\/>\n   &#8211; <strong>Likely service area:<\/strong> DevOps consulting (verify on site)<br\/>\n   &#8211; <strong>Where they may help:<\/strong> Platform enablement, automation, governance patterns for cloud deployments<br\/>\n   &#8211; <strong>Consulting use case examples:<\/strong> <\/p>\n<ul>\n<li>Defining compartment\/IAM\/tagging standards for Marketplace deployments  <\/li>\n<li>Cost optimization assessment for stacks that deploy multiple OCI services  <\/li>\n<li><strong>Website:<\/strong> https:\/\/devopsconsulting.in\/<\/li>\n<\/ul>\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 Marketplace Guide<\/h3>\n\n\n\n<p>To use Marketplace Guide effectively on Oracle Cloud, learn these OCI basics first:\n&#8211; OCI tenancy structure: <strong>regions, compartments, VCNs<\/strong>\n&#8211; IAM fundamentals: <strong>users, groups, policies, dynamic groups<\/strong>\n&#8211; Compute basics: instances, shapes, boot volumes, SSH access\n&#8211; Networking: subnets, route tables, internet gateway, NAT gateway, NSGs\/security lists\n&#8211; Cost basics: budgets, tagging, service limits<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Marketplace Guide<\/h3>\n\n\n\n<p>To run Marketplace deployments professionally:\n&#8211; <strong>OCI Resource Manager \/ Terraform<\/strong>: plans, applies, state, drift, modules\n&#8211; Observability:\n  &#8211; OCI Monitoring\/Alarms\n  &#8211; OCI Logging and log analytics approaches (service availability varies)\n&#8211; Security:\n  &#8211; Vault and KMS\n  &#8211; Vulnerability scanning (service availability varies; verify)\n  &#8211; WAF and secure ingress patterns\n&#8211; Reliability:\n  &#8211; HA patterns for OCI (multi-AD where available, multi-FD)\n  &#8211; Backup and restore testing\n&#8211; FinOps:\n  &#8211; cost allocation with tags\n  &#8211; usage reporting and chargeback\/showback<\/p>\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 \/ OCI engineer<\/li>\n<li>Solutions architect<\/li>\n<li>DevOps engineer<\/li>\n<li>SRE \/ Platform engineer<\/li>\n<li>Security engineer (cloud security, network security)<\/li>\n<li>FinOps analyst (for governance and spend control)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle offers OCI certifications (associate\/professional tracks). Marketplace-specific certification is not commonly separated; instead:\n&#8211; Start with foundational OCI certs (verify current certification names and tracks on Oracle University).\n&#8211; Add architecture and security certifications as your responsibilities grow.<br\/>\nVerify current OCI certifications here: https:\/\/education.oracle.com\/<\/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 \u201capproved Marketplace listings\u201d internal page with:<\/li>\n<li>required compartments<\/li>\n<li>required tags<\/li>\n<li>baseline network architecture<\/li>\n<li>Create a reusable Terraform \u201clanding zone\u201d that Marketplace stacks must deploy into (shared VCN patterns).<\/li>\n<li>Implement cost guardrails:<\/li>\n<li>budgets<\/li>\n<li>quota policies (where applicable)<\/li>\n<li>automated cleanup for lab compartments<\/li>\n<li>Run a security review checklist on a Marketplace image:<\/li>\n<li>open ports<\/li>\n<li>default users<\/li>\n<li>patch status<\/li>\n<li>logging configuration<\/li>\n<\/ul>\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 IaaS\/PaaS platform used to run compute, networking, storage, and managed services.<\/li>\n<li><strong>Marketplace listing:<\/strong> A catalog entry describing a solution (image\/stack\/software) available to deploy or subscribe to.<\/li>\n<li><strong>Subscription \/ terms acceptance:<\/strong> The action of accepting a listing\u2019s license terms so it can be deployed in a tenancy.<\/li>\n<li><strong>Compartment:<\/strong> An OCI logical container for organizing and isolating resources with IAM policies.<\/li>\n<li><strong>VCN (Virtual Cloud Network):<\/strong> OCI virtual network containing subnets, route tables, gateways, and security rules.<\/li>\n<li><strong>NSG (Network Security Group):<\/strong> Security rules applied to groups of VNICs for finer-grained network control.<\/li>\n<li><strong>Security list:<\/strong> Subnet-level ingress\/egress rules (older model; still used).<\/li>\n<li><strong>Resource Manager:<\/strong> OCI managed Terraform service for provisioning infrastructure using stacks and jobs.<\/li>\n<li><strong>Stack:<\/strong> A Terraform configuration packaged for Resource Manager deployment.<\/li>\n<li><strong>Plan\/Apply\/Destroy:<\/strong> Terraform lifecycle actions: preview changes, create\/update resources, and delete resources.<\/li>\n<li><strong>BYOL:<\/strong> Bring Your Own License\u2014use your existing software license with a Marketplace deployment.<\/li>\n<li><strong>Metered billing:<\/strong> Consumption-based charges for software licensing integrated into billing (availability depends on listing).<\/li>\n<li><strong>Always Free:<\/strong> OCI free tier resources that can be used indefinitely within limits (verify current eligibility).<\/li>\n<li><strong>Egress:<\/strong> Outbound network traffic from OCI to the internet or other regions; often a cost driver.<\/li>\n<li><strong>Golden image:<\/strong> A standardized, hardened VM image maintained internally by an organization.<\/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>Marketplace Guide<\/strong> (Oracle Cloud Marketplace) is your entry point for discovering, subscribing to, and deploying software solutions on <strong>Oracle Cloud<\/strong> using prebuilt images and Terraform-based stacks. It matters because it shortens delivery timelines, supports standardization, and connects solution procurement with practical deployment workflows.<\/p>\n\n\n\n<p>Cost and security outcomes depend less on the Marketplace catalog itself and more on what you deploy: compute shapes, load balancers, storage, network egress, and any publisher licensing. Use compartments, least-privilege IAM, strict network controls, tagging, and budget alerts to keep Marketplace deployments safe and predictable.<\/p>\n\n\n\n<p>Use Marketplace Guide when you want a repeatable, supported starting point and you can align licensing\/support with your operational model. Avoid it when strict compliance demands fully internal builds or when the listing\u2019s architecture doesn\u2019t fit production requirements.<\/p>\n\n\n\n<p>Next step: pick one free listing in your region, deploy it into a lab compartment using the tutorial above, then practice hardening it\u2014private subnets, Bastion access, Vault for secrets, alarms, and a clean destroy workflow.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Marketplace<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[71,62],"tags":[],"class_list":["post-928","post","type-post","status-publish","format-standard","hentry","category-marketplace","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/928","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=928"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/928\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=928"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=928"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}