{"id":930,"date":"2026-04-17T04:21:45","date_gmt":"2026-04-17T04:21:45","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-using-marketplace-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace\/"},"modified":"2026-04-17T04:21:45","modified_gmt":"2026-04-17T04:21:45","slug":"oracle-cloud-using-marketplace-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-using-marketplace-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-marketplace\/","title":{"rendered":"Oracle Cloud Using Marketplace 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>Using Marketplace<\/strong> is the practical workflow of discovering, evaluating, subscribing to, and deploying third\u2011party (and Oracle\u2011published) solutions from <strong>Oracle Cloud Marketplace<\/strong> into your Oracle Cloud tenancy.<\/p>\n\n\n\n<p>In simple terms: <strong>Marketplace is a catalog of ready-to-deploy software and cloud solutions<\/strong>. Using Marketplace means you can launch curated VM images, deploy Terraform\/Resource Manager stacks, or subscribe to SaaS offers without building everything from scratch.<\/p>\n\n\n\n<p>Technically, Oracle Cloud Marketplace integrates with core Oracle Cloud Infrastructure (OCI) services such as <strong>Compute<\/strong>, <strong>Networking (VCN)<\/strong>, and <strong>Resource Manager<\/strong>. Marketplace listings include publisher-provided artifacts (images, stacks, SaaS links), pricing\/terms, and deployment instructions; when you deploy, the underlying OCI services create resources in your compartments using your IAM permissions.<\/p>\n\n\n\n<p><strong>The problem it solves:<\/strong> teams waste time and introduce risk when they manually assemble common infrastructure\/software patterns. Using Marketplace accelerates deployments, standardizes acquisition and licensing, and provides a governed path to deploy vendor solutions\u2014while keeping deployment within your tenancy and IAM controls.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Using Marketplace?<\/h2>\n\n\n\n<p><strong>Using Marketplace<\/strong> (in Oracle Cloud, under the <strong>Marketplace<\/strong> category) is the end-to-end process of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Browsing and searching Marketplace listings<\/li>\n<li>Reviewing publisher details, documentation, and support<\/li>\n<li>Accepting terms and (if applicable) subscribing to paid usage or BYOL licensing<\/li>\n<li>Deploying a solution into your tenancy (for images\/stacks) or activating an external SaaS subscription<\/li>\n<li>Managing the lifecycle (updates, scaling, monitoring, security posture, and cost) using OCI services<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose (service scope)<\/h3>\n\n\n\n<p>Oracle Cloud Marketplace\u2019s purpose is to provide a catalog of <strong>partner and Oracle solutions<\/strong> that can be deployed or subscribed to, with clear terms and (where applicable) integrated billing.<\/p>\n\n\n\n<blockquote>\n<p>Verify the most current Marketplace overview and \u201cUsing Marketplace\u201d documentation in official docs:<br\/>\nhttps:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Discovery &amp; evaluation:<\/strong> search, filter, compare solutions; review documentation and support information.<\/li>\n<li><strong>Subscription &amp; governance:<\/strong> accept terms, track subscriptions\/offers, and align to procurement processes.<\/li>\n<li><strong>Deployment:<\/strong> deploy supported listing types (commonly VM images and Resource Manager stacks) into OCI resources you control.<\/li>\n<li><strong>Billing integration (when applicable):<\/strong> some listings bill via OCI usage; others are BYOL or external billing.<\/li>\n<li><strong>Operational integration:<\/strong> deployed resources are managed using standard OCI primitives (instances, VCNs, load balancers, etc.).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Marketplace Console experience:<\/strong> where you search listings, review details, and initiate deployment.<\/li>\n<li><strong>Listings:<\/strong> the catalog entries (each with publisher info, pricing model, and deployment artifacts).<\/li>\n<li><strong>Agreements\/terms acceptance:<\/strong> required before deployment\/subscription.<\/li>\n<li><strong>Deployment artifacts (by listing type):<\/strong><\/li>\n<li><strong>Images<\/strong> (VM images that run on OCI Compute)<\/li>\n<li><strong>Stacks<\/strong> (often Terraform configurations deployable via OCI Resource Manager)<\/li>\n<li><strong>SaaS \/ services<\/strong> (subscription workflows that may redirect to publisher systems)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<p>Marketplace is primarily a <strong>catalog + subscription + deployment integration layer<\/strong>, not a standalone runtime like Compute or Storage. The actual runtime is provided by underlying OCI services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scope: regional\/global\/tenancy<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Marketplace catalog access<\/strong> is available through the Oracle Cloud Console (availability depends on tenancy configuration and region; verify in official docs).<\/li>\n<li><strong>Deployments are region-bound<\/strong> because resources like Compute instances, VCNs, and load balancers are created in a specific OCI region.<\/li>\n<li><strong>Subscriptions\/agreements<\/strong> are typically <strong>tenancy-scoped<\/strong> (and may have region-specific constraints depending on the listing). Always read the listing terms.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Oracle Cloud ecosystem<\/h3>\n\n\n\n<p>Using Marketplace sits at the \u201cfront door\u201d of solution acquisition and deployment, integrating with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Identity and Access Management (IAM):<\/strong> who can subscribe\/deploy<\/li>\n<li><strong>Compartments &amp; tagging:<\/strong> where resources are created and how they\u2019re governed<\/li>\n<li><strong>Compute \/ VCN \/ Load Balancer \/ Block Volumes:<\/strong> typical runtime targets<\/li>\n<li><strong>Resource Manager (Terraform):<\/strong> infrastructure-as-code deployment for stacks<\/li>\n<li><strong>Logging \/ Monitoring \/ Audit:<\/strong> operational visibility and governance<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Using Marketplace?<\/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 time-to-value:<\/strong> deploy vetted solutions quickly rather than building everything from scratch.<\/li>\n<li><strong>Procurement alignment:<\/strong> listing terms, licensing approaches (BYOL\/metered), and billing integration can simplify purchasing (exact mechanics vary by listing).<\/li>\n<li><strong>Vendor ecosystems:<\/strong> access partner solutions commonly required for enterprise workloads (security, networking, databases, analytics, DevOps tooling).<\/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>Reference architectures \u201cpackaged\u201d into deployables:<\/strong> many solutions ship as images or IaC stacks that represent known-good patterns.<\/li>\n<li><strong>Repeatable deployments:<\/strong> stacks reduce \u201csnowflake\u201d infrastructure and increase consistency.<\/li>\n<li><strong>Integration with OCI primitives:<\/strong> deployments create standard OCI resources you can manage with your existing toolchain.<\/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>Standard lifecycle management:<\/strong> once deployed, resources are managed like any OCI resource (patching, backups, scaling).<\/li>\n<li><strong>Support clarity:<\/strong> listings typically define who supports what (publisher vs Oracle vs shared responsibility).<\/li>\n<li><strong>Fewer manual steps:<\/strong> preconfigured images and templates reduce operational toil.<\/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>Governed access:<\/strong> IAM policies and compartments help constrain who can deploy what and where.<\/li>\n<li><strong>Traceability:<\/strong> OCI Audit logs actions such as resource creation and configuration changes.<\/li>\n<li><strong>Reduced supply-chain ambiguity (when used correctly):<\/strong> Marketplace provides publisher identity and a consistent acquisition path. (You still must validate publisher, artifacts, and configurations.)<\/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><strong>Production-grade patterns:<\/strong> many listings assume scale-out designs and integrate with load balancers, autoscaling, and HA topologies.<\/li>\n<li><strong>Right-size from day one:<\/strong> templates often include sizing guidance (verify each listing).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose Using Marketplace when:\n&#8211; You need a standard solution quickly (e.g., firewall appliance, CI runner, logging agent, API gateway, CMS, VPN).\n&#8211; You want an IaC-based deployment that your platform team can standardize.\n&#8211; You need commercial software with a defined licensing model and support channel.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Avoid or be cautious when:\n&#8211; You cannot validate the publisher, supportability, or security posture.\n&#8211; The listing forces a licensing model that conflicts with your procurement rules.\n&#8211; Your environment requires very tight hardening and you can\u2019t verify image provenance and update cadence.\n&#8211; You can achieve the same outcome with simpler native services (lower operational burden) or your existing golden images and templates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Using Marketplace 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 connectors, secure access gateways, hardened images<\/li>\n<li><strong>Healthcare:<\/strong> compliance-focused deployments, secure data movement tooling<\/li>\n<li><strong>Retail\/eCommerce:<\/strong> CMS, caching layers, WAF\/security, observability<\/li>\n<li><strong>Manufacturing\/IoT:<\/strong> edge data ingestion tooling, messaging stacks<\/li>\n<li><strong>Public sector:<\/strong> compliant images, vendor-certified solutions (verify certification claims per listing)<\/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 standardizing \u201capproved\u201d deployments<\/li>\n<li>DevOps\/SRE teams accelerating environment provisioning<\/li>\n<li>Security teams deploying network\/security appliances and scanners<\/li>\n<li>Application teams needing packaged runtimes (CMS, API gateways, app servers)<\/li>\n<li>Architects evaluating vendor solutions and integration patterns<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Security &amp; networking:<\/strong> firewalls, VPN, IDS\/IPS, WAF integration components<\/li>\n<li><strong>Observability:<\/strong> logging\/monitoring agents, APM components, SIEM forwarding<\/li>\n<li><strong>Dev tooling:<\/strong> CI agents, artifact caching, configuration tooling<\/li>\n<li><strong>Web workloads:<\/strong> WordPress-like stacks, reverse proxies, web servers (listing availability varies)<\/li>\n<li><strong>Data &amp; integration:<\/strong> connectors, ETL tools, message brokers (often via stacks)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Single-instance dev\/test proofs of concept<\/li>\n<li>Multi-tier production systems (LB + app tier + DB)<\/li>\n<li>Hub-and-spoke networks with security appliances in shared services compartments<\/li>\n<li>IaC-driven landing zones where Marketplace stacks are integrated into pipelines<\/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> fastest path to a working environment; focus on cost controls and cleanup.<\/li>\n<li><strong>Production:<\/strong> requires governance: IAM, network segmentation, patching strategy, observability, backups, DR, and vendor support plans.<\/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, OCI-aligned scenarios for Using Marketplace. Availability and exact steps vary by listing\u2014always confirm in the listing documentation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Deploy a vendor security appliance in a DMZ<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need a next-generation firewall or IDS in front of workloads quickly.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Vendors provide certified images and deployment guides.<\/li>\n<li><strong>Scenario:<\/strong> Deploy appliance VM(s) into a dedicated VCN subnet, integrate with route tables and NSGs, and steer traffic through it.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Launch a prebuilt developer workstation image<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Engineers need consistent toolchains without days of setup.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Images can ship with curated tooling and versions.<\/li>\n<li><strong>Scenario:<\/strong> Launch a developer VM image, connect via SSH, and use it as a build\/test box.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Deploy an application via Resource Manager stack (Terraform)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Manual provisioning is error-prone and inconsistent.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Stacks encode infrastructure patterns as code.<\/li>\n<li><strong>Scenario:<\/strong> Deploy a stack that creates VCN, compute, and security rules with parameterized inputs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Evaluate a commercial software trial quickly<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Procurement and setup time delays technical evaluation.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Listings may support trials or quick starts.<\/li>\n<li><strong>Scenario:<\/strong> Subscribe to a listing, deploy into a sandbox compartment, and test against requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Standardize \u201capproved\u201d images for regulated environments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Teams deploy random images that fail audits.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Centralized catalog with publisher identity and consistent access.<\/li>\n<li><strong>Scenario:<\/strong> Security team approves a hardened image listing; platform team restricts deployments to that image.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Deploy a monitoring\/agent gateway for hybrid workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need agent infrastructure to forward logs\/metrics from on-prem to OCI.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Some vendors package gateways\/collectors.<\/li>\n<li><strong>Scenario:<\/strong> Deploy a collector VM in a private subnet with outbound access to vendor endpoints or OCI services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Spin up a proof-of-concept web app stack<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need a working web app quickly for demos.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Prebuilt stacks can include reverse proxy, app tier, and database integration.<\/li>\n<li><strong>Scenario:<\/strong> Deploy a stack into an Always Free-eligible shape (where possible) and validate functionality.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Deploy a data movement or backup connector<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need consistent backups or data transfer tooling.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Vendors provide appliances or templates integrated with object storage.<\/li>\n<li><strong>Scenario:<\/strong> Deploy connector, configure Object Storage bucket, schedule transfers.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Roll out consistent CI runners in OCI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> CI runners need consistent dependencies and scaling.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Some listings provide runner images\/templates.<\/li>\n<li><strong>Scenario:<\/strong> Deploy runners into a dedicated compartment with autoscaling rules and restricted network egress.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Build a reference architecture baseline faster<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Architects need a \u201cknown-good\u201d baseline to start projects.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Marketplace stacks often represent reference architectures.<\/li>\n<li><strong>Scenario:<\/strong> Deploy baseline networking + compute + logging stack, then layer applications.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Deploy an API gateway or ingress controller pattern<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need standardized ingress and routing policies.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Some solutions ship as stacks\/images with documented patterns.<\/li>\n<li><strong>Scenario:<\/strong> Deploy gateway tier behind OCI Load Balancer and integrate with private backends.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Create a training lab environment for teams<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need repeatable labs for onboarding.<\/li>\n<li><strong>Why Marketplace fits:<\/strong> Stacks provide repeatable infrastructure and cleanup.<\/li>\n<li><strong>Scenario:<\/strong> Instructors deploy identical environments per cohort and tear down after training.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Marketplace features evolve; confirm exact capabilities in current Oracle Cloud docs and the Console.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6.1 Listing discovery (search, categories, filters)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Helps you find solutions by category, publisher, price model, and other metadata.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces time spent validating random internet images or scripts.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster shortlist creation for architecture decisions.<\/li>\n<li><strong>Caveats:<\/strong> Not every listing is available in every region; availability can vary.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.2 Listing details: documentation, architecture, and support info<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides publisher documentation, deployment guides, support channels, and terms.<\/li>\n<li><strong>Why it matters:<\/strong> Clarifies responsibility boundaries and prerequisites.<\/li>\n<li><strong>Benefit:<\/strong> Better operational planning and fewer \u201cunknowns\u201d.<\/li>\n<li><strong>Caveats:<\/strong> Quality varies by publisher; validate and test.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.3 Terms acceptance and subscription flow<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Requires users to accept legal terms before deploying\/using a listing.<\/li>\n<li><strong>Why it matters:<\/strong> Helps align with licensing and compliance requirements.<\/li>\n<li><strong>Benefit:<\/strong> Traceable governance step.<\/li>\n<li><strong>Caveats:<\/strong> Some organizations require procurement review before acceptance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.4 Multiple pricing models (listing-dependent)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Supports listings that are free, BYOL, or billed based on usage\/subscription.<\/li>\n<li><strong>Why it matters:<\/strong> You can align to your budget model and licensing posture.<\/li>\n<li><strong>Benefit:<\/strong> Flexibility.<\/li>\n<li><strong>Caveats:<\/strong> Pricing is listing-specific; do not assume \u201cfree\u201d means \u201cno costs\u201d (compute\/network still apply).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.5 Deployment to OCI resources (Images)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Launches a Compute instance from a publisher image.<\/li>\n<li><strong>Why it matters:<\/strong> Speeds setup of complex software.<\/li>\n<li><strong>Benefit:<\/strong> Reduced manual installation\/configuration.<\/li>\n<li><strong>Caveats:<\/strong> You still own patching and hardening unless the listing states otherwise.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.6 Deployment via OCI Resource Manager (Stacks)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Uses Terraform-based templates to create multiple OCI resources.<\/li>\n<li><strong>Why it matters:<\/strong> Repeatable, auditable infrastructure.<\/li>\n<li><strong>Benefit:<\/strong> Faster production-like provisioning.<\/li>\n<li><strong>Caveats:<\/strong> Review templates carefully; they may create billable resources and open network paths.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.7 Integration with compartments and tagging (governance)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lets you deploy into specific compartments and apply tags (depending on resource types created).<\/li>\n<li><strong>Why it matters:<\/strong> Cost allocation and policy enforcement.<\/li>\n<li><strong>Benefit:<\/strong> Cleaner operations and chargeback\/showback.<\/li>\n<li><strong>Caveats:<\/strong> Tagging discipline is on you; templates may not tag everything by default.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.8 Auditability via OCI Audit (indirect but critical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Actions taken in OCI (creating instances, VCNs, etc.) are captured by Audit.<\/li>\n<li><strong>Why it matters:<\/strong> You need traceability for security investigations and compliance.<\/li>\n<li><strong>Benefit:<\/strong> Forensics and accountability.<\/li>\n<li><strong>Caveats:<\/strong> Ensure Audit is retained and monitored according to your policy.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.9 Publisher ecosystem and updates (listing-dependent)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Publishers may update images\/stacks over time.<\/li>\n<li><strong>Why it matters:<\/strong> Updates can address vulnerabilities and add features.<\/li>\n<li><strong>Benefit:<\/strong> Better security posture if you stay current.<\/li>\n<li><strong>Caveats:<\/strong> Updates are not automatically applied to your running instances unless you patch\/upgrade.<\/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\">7.1 High-level architecture<\/h3>\n\n\n\n<p>At a high level, Using Marketplace involves:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>User<\/strong> searches Marketplace in the OCI Console.<\/li>\n<li>User <strong>selects a listing<\/strong>, reviews details, and accepts terms.<\/li>\n<li>User chooses <strong>deployment method<\/strong> (commonly: launch image to Compute or deploy stack via Resource Manager).<\/li>\n<li>OCI provisions resources in the selected <strong>compartment and region<\/strong>.<\/li>\n<li>You operate the deployed resources with standard OCI tools (Console, CLI, SDK, monitoring\/logging).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">7.2 Request\/data\/control flow<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane:<\/strong> Console\/API calls for Marketplace subscription and for provisioning OCI resources.<\/li>\n<li><strong>Data plane:<\/strong> Traffic to\/from deployed instances\/services in your VCN (e.g., inbound HTTP to a VM, outbound updates to repos).<\/li>\n<li><strong>Billing flow:<\/strong> If listing is paid through OCI, usage records flow into OCI billing; otherwise billing may happen externally (listing-specific).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.3 Integrations with related services<\/h3>\n\n\n\n<p>Common integrations include:\n&#8211; <strong>OCI Compute:<\/strong> Marketplace images run as VM instances.\n&#8211; <strong>OCI Resource Manager:<\/strong> stacks deploy Terraform-managed infrastructure.\n&#8211; <strong>OCI Networking (VCN, subnets, IGW\/NAT\/Service Gateway):<\/strong> connectivity for instances and applications.\n&#8211; <strong>OCI Vault:<\/strong> store secrets (recommended for production).\n&#8211; <strong>OCI Logging and Monitoring:<\/strong> collect logs\/metrics from deployed components.\n&#8211; <strong>OCI Bastion:<\/strong> reduce need for public SSH exposure (recommended).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7.4 Dependency services<\/h3>\n\n\n\n<p>Using Marketplace typically depends on:\n&#8211; <strong>IAM<\/strong> (users, groups, policies)\n&#8211; <strong>Compartments<\/strong>\n&#8211; <strong>Target runtime services<\/strong> (Compute, VCN, LB, OKE, etc.) depending on listing type<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7.5 Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Users authenticate to OCI using <strong>IAM<\/strong> (local users, federation, SSO, etc.).<\/li>\n<li>Authorization is enforced via <strong>IAM policies<\/strong> at tenancy\/compartment scope.<\/li>\n<li>Deployments inherit the permissions of the user (or group) performing the action.<\/li>\n<\/ul>\n\n\n\n<blockquote>\n<p>Exact IAM policy verbs\/resources for Marketplace can change; <strong>verify the current IAM policy reference in official docs<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">7.6 Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Marketplace itself is a control-plane experience.<\/li>\n<li>Deployed resources live inside your VCN and follow your network design:<\/li>\n<li>Public subnets + Internet Gateway for public endpoints (use cautiously)<\/li>\n<li>Private subnets + NAT\/Service Gateway for controlled egress<\/li>\n<li>NSGs\/Security Lists to constrain flows<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.7 Monitoring\/logging\/governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Monitoring<\/strong> for metrics and alarms.<\/li>\n<li>Use <strong>OCI Logging<\/strong> for OS\/app logs (agent-based if needed).<\/li>\n<li>Use <strong>OCI Audit<\/strong> to track provisioning and configuration actions.<\/li>\n<li>Use <strong>tags<\/strong> (cost-tracking and governance) and <strong>budgets<\/strong> where applicable.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Engineer \/ Admin] --&gt; C[OCI Console]\n  C --&gt; M[Oracle Cloud Marketplace]\n  M --&gt;|Launch Image \/ Deploy Stack| P[OCI Provisioning APIs]\n  P --&gt; CMP[Compute Instance]\n  P --&gt; NET[VCN\/Subnet\/NSG]\n  CMP --&gt; APP[Installed Marketplace Software]\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Identity\n    IDP[Enterprise IdP \/ Federation]\n    IAM[OCI IAM]\n    IDP --&gt; IAM\n  end\n\n  subgraph Governance\n    CMPA[Compartments]\n    TAG[Tags &amp; Tag Defaults]\n    AUD[OCI Audit]\n  end\n\n  subgraph Marketplace\n    MKTP[OCI Marketplace Listing]\n    TERMS[Terms \/ Subscription]\n    MKTP --&gt; TERMS\n  end\n\n  subgraph Deployment\n    RM[OCI Resource Manager (Terraform)]\n    VCN[VCN]\n    PUB[Public Subnet]\n    PRI[Private Subnet]\n    LB[Load Balancer]\n    APP1[App VM(s) from Marketplace Image]\n    BAST[OCI Bastion]\n    VAULT[OCI Vault]\n    LOG[OCI Logging]\n    MON[OCI Monitoring]\n  end\n\n  IAM --&gt; MKTP\n  IAM --&gt; RM\n  TERMS --&gt; RM\n\n  RM --&gt; VCN\n  VCN --&gt; PUB\n  VCN --&gt; PRI\n  RM --&gt; LB\n  RM --&gt; APP1\n  RM --&gt; BAST\n  RM --&gt; VAULT\n\n  LB --&gt; APP1\n  BAST --&gt; APP1\n  APP1 --&gt; LOG\n  APP1 --&gt; MON\n\n  AUD --&gt; RM\n  CMPA --&gt; RM\n  TAG --&gt; RM\n<\/code><\/pre>\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 active <strong>Oracle Cloud (OCI) tenancy<\/strong><\/li>\n<li>Ability to access <strong>Marketplace<\/strong> in the OCI Console<\/li>\n<li>A target <strong>region<\/strong> where you will deploy resources<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM<\/h3>\n\n\n\n<p>You typically need permission to:\n&#8211; View and subscribe\/accept terms for Marketplace listings\n&#8211; Create and manage required OCI resources (commonly: Compute, VCN, subnets, NSGs, block volumes, load balancer)\n&#8211; Use or manage Resource Manager stacks (for stack-based listings)<\/p>\n\n\n\n<p>Because IAM policy details can vary and are frequently refined, <strong>verify the current required permissions in official Marketplace\/IAM documentation<\/strong>:\n&#8211; Marketplace docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<br\/>\n&#8211; IAM docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/home.htm<\/p>\n\n\n\n<p>Practical guidance:\n&#8211; For labs, a user in an <strong>Administrators<\/strong> group (or equivalent broad permissions) is simplest.\n&#8211; For production, create a dedicated group (e.g., <code>Marketplace-Deployer<\/code>) and scope policies to specific compartments.<\/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 billing-enabled tenancy is often required to deploy paid listings and sometimes even to launch resources (Compute\/storage) even if the listing is free.<\/li>\n<li>For Always Free usage, ensure your account is eligible and you choose Always Free-capable resources (verify Always Free rules).<\/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><strong>OCI Console<\/strong> (required for the simplest flow)<\/li>\n<li><strong>OCI CLI<\/strong> (optional, useful for verification and cleanup): https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/Concepts\/cliconcepts.htm<\/li>\n<li><strong>SSH client<\/strong> (for VM access)<\/li>\n<li><strong>Terraform knowledge<\/strong> (if using Resource Manager stacks)<\/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 listing availability can vary by region.<\/li>\n<li>Some publishers restrict deployments to certain regions.<\/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>Your tenancy may have service limits on Compute instances, OCPUs, VNICs, block volumes, etc.<\/li>\n<li>If a deployment fails unexpectedly, check service limits and quotas first.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>VCN<\/strong> and subnets (or use a wizard to create them)<\/li>\n<li><strong>Compute<\/strong> for VM-based images<\/li>\n<li><strong>Resource Manager<\/strong> for stack deployments<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Marketplace costs are <strong>listing-dependent<\/strong> and the runtime costs depend on what you deploy.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.1 Pricing dimensions (how charges can happen)<\/h3>\n\n\n\n<p>Marketplace listings commonly fall into one of these pricing patterns:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Free listing<\/strong><br\/>\n   &#8211; No additional publisher charge via Marketplace<br\/>\n   &#8211; <strong>You still pay for OCI resources<\/strong> you deploy (Compute, storage, load balancer, egress, etc.)<\/p>\n<\/li>\n<li>\n<p><strong>BYOL (Bring Your Own License)<\/strong><br\/>\n   &#8211; You provide your own license agreement with the vendor<br\/>\n   &#8211; You pay OCI infrastructure costs<br\/>\n   &#8211; Vendor costs are handled outside OCI billing (typically)<\/p>\n<\/li>\n<li>\n<p><strong>Paid listing billed through OCI (metered\/subscription)<\/strong><br\/>\n   &#8211; Publisher software charges may appear as part of OCI billing (exact billing mechanics vary)\n   &#8211; Plus OCI infrastructure costs<\/p>\n<\/li>\n<li>\n<p><strong>SaaS subscription (external)<\/strong><br\/>\n   &#8211; Marketplace may facilitate discovery and subscription, but billing and runtime are external<br\/>\n   &#8211; You might still deploy connectors\/agents inside OCI that incur OCI costs<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p>Always read:\n&#8211; Listing pricing tab\/section\n&#8211; Terms and conditions\n&#8211; Any additional docs from the publisher<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.2 Free tier \/ Always Free considerations<\/h3>\n\n\n\n<p>Oracle Cloud offers an Always Free tier for certain services in eligible tenancies\/regions, but <strong>Marketplace listings are not inherently \u201cAlways Free\u201d<\/strong>. If you deploy Marketplace software onto Always Free-eligible shapes and minimal storage, your <strong>OCI infrastructure<\/strong> might stay within Always Free limits.<\/p>\n\n\n\n<p>Verify Always Free: https:\/\/www.oracle.com\/cloud\/free\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.3 Cost drivers (direct and indirect)<\/h3>\n\n\n\n<p><strong>Direct OCI cost drivers (most common):<\/strong>\n&#8211; Compute instance shape (OCPU count, memory)\n&#8211; Boot and block volume size\/performance\n&#8211; Load balancers (if created)\n&#8211; Outbound data transfer (egress)\n&#8211; NAT Gateway usage (if used)\n&#8211; Object Storage usage (if the solution stores backups\/artifacts)<\/p>\n\n\n\n<p><strong>Direct Marketplace\/publisher cost drivers (listing-dependent):<\/strong>\n&#8211; Hourly metered software fees\n&#8211; Per-instance license fees\n&#8211; Support tier selection<\/p>\n\n\n\n<p><strong>Indirect costs:<\/strong>\n&#8211; Operational overhead (patching, backups, monitoring)\n&#8211; Additional environments (dev\/test\/prod)\n&#8211; High availability duplicates (2+ instances across fault domains\/ADs)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.4 Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Internet egress is a common surprise cost driver for:<\/li>\n<li>OS updates and package downloads<\/li>\n<li>External SaaS calls<\/li>\n<li>Log shipping to external systems<\/li>\n<li>Prefer:<\/li>\n<li>Private connectivity patterns where possible<\/li>\n<li>Regional endpoints<\/li>\n<li>Controlled egress via NAT and allowlists<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.5 How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with the smallest shape that meets requirements.<\/li>\n<li>Prefer <strong>free listings<\/strong> for evaluation.<\/li>\n<li>Stop\/terminate instances when not in use.<\/li>\n<li>Use tagging and budgets to track Marketplace-related spend.<\/li>\n<li>Review stack templates to remove unneeded billable components (e.g., load balancer) before production rollout.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.6 Example low-cost starter estimate (no fabricated numbers)<\/h3>\n\n\n\n<p>A typical low-cost evaluation might include:\n&#8211; 1 small VM instance from a free Marketplace image\n&#8211; 1 boot volume (minimal size)\n&#8211; A basic VCN with a public subnet for SSH (or use Bastion)\n&#8211; Minimal outbound data<\/p>\n\n\n\n<p>Exact cost depends on:\n&#8211; Region\n&#8211; Shape and hours run\n&#8211; Storage size and performance\n&#8211; Egress volume\n&#8211; Whether the listing has paid software fees<\/p>\n\n\n\n<p>Use official pricing resources:\n&#8211; OCI pricing overview\/price list: https:\/\/www.oracle.com\/cloud\/price-list\/\n&#8211; OCI cost estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.7 Example production cost considerations<\/h3>\n\n\n\n<p>In production, costs usually rise due to:\n&#8211; High availability (multiple instances, multiple subnets, potentially multiple regions)\n&#8211; Load balancers and WAF\n&#8211; Larger block volumes and backups\n&#8211; Logging\/monitoring retention\n&#8211; Paid software licensing\/support<\/p>\n\n\n\n<p>Recommendation: run a cost model that separates:\n&#8211; <strong>OCI infrastructure<\/strong> (compute\/storage\/networking)\n&#8211; <strong>Publisher software charges<\/strong> (if billed through OCI)\n&#8211; <strong>Operational overhead<\/strong> (people\/process\/tools)<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab shows a safe, beginner-friendly workflow for <strong>Using Marketplace<\/strong> by launching a Marketplace image as a Compute instance, verifying access, and cleaning up.<\/p>\n\n\n\n<p>Because Marketplace listings change over time and vary by region, the tutorial uses a \u201cchoose a free image\u201d approach and calls out what to verify.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Deploy a <strong>free Marketplace image<\/strong> into Oracle Cloud (OCI), connect via SSH, verify the instance is running, and then clean up all resources to avoid ongoing costs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create a compartment for the lab (optional but recommended)\n2. Create a VCN (network) using a wizard\n3. In Marketplace, select a <strong>Free<\/strong> image listing and launch a Compute instance\n4. Verify the instance is reachable over SSH\n5. Validate basic system state\n6. Clean up resources<\/p>\n\n\n\n<p>Expected time: 30\u201360 minutes<br\/>\nCost: Low, but depends on shape and runtime hours. Stop\/terminate afterward.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Create a compartment (recommended)<\/h3>\n\n\n\n<p><strong>Why:<\/strong> Keeps lab resources isolated for cleanup and access control.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the Oracle Cloud Console.<\/li>\n<li>Go to <strong>Identity &amp; Security<\/strong> \u2192 <strong>Compartments<\/strong>.<\/li>\n<li>Click <strong>Create Compartment<\/strong>.<\/li>\n<li>Name: <code>cmp-mkt-lab<\/code><br\/>\n   Description: <code>Marketplace lab resources<\/code><br\/>\n   Parent compartment: choose appropriately (often the root compartment for labs).<\/li>\n<li>Click <strong>Create Compartment<\/strong>.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A new compartment appears and is in \u201cActive\u201d state.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Confirm you can select <code>cmp-mkt-lab<\/code> from the compartment selector.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create networking (VCN) with a wizard<\/h3>\n\n\n\n<p><strong>Why:<\/strong> Most VM images need a VCN + subnet to attach.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Networking<\/strong> \u2192 <strong>Virtual Cloud Networks<\/strong>.<\/li>\n<li>Select compartment: <code>cmp-mkt-lab<\/code>.<\/li>\n<li>Click <strong>Create VCN<\/strong>.<\/li>\n<li>Choose a wizard option such as <strong>VCN with Internet Connectivity<\/strong> (names may vary slightly).<\/li>\n<li>\n<p>Keep defaults for a lab, and ensure it creates:\n   &#8211; VCN\n   &#8211; Public subnet\n   &#8211; Internet Gateway\n   &#8211; Route table rule to the Internet Gateway\n   &#8211; Security list allowing required ingress (often SSH)<\/p>\n<\/li>\n<li>\n<p>Click <strong>Create<\/strong>.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A VCN with at least one public subnet.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Open the VCN \u2192 confirm:\n  &#8211; Internet Gateway exists\n  &#8211; Public subnet exists\n  &#8211; Route rule includes <code>0.0.0.0\/0<\/code> to Internet Gateway<\/p>\n\n\n\n<p><strong>Cost note:<\/strong> VCN itself is generally not the cost driver; compute and egress are. Verify current pricing rules in official docs if needed.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Choose a free Marketplace image listing<\/h3>\n\n\n\n<p><strong>Why:<\/strong> Marketplace images provide prebuilt software environments.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Marketplace<\/strong> in the OCI Console.<\/li>\n<li>Ensure you are in the correct region (top bar).<\/li>\n<li>Search for a listing that meets these lab criteria:\n   &#8211; <strong>Type:<\/strong> Image (VM image)\n   &#8211; <strong>Price:<\/strong> Free (or $0 software fee)\n   &#8211; <strong>Publisher:<\/strong> Prefer Oracle or a well-known vendor\n   &#8211; <strong>Documentation:<\/strong> Has clear deployment steps<\/li>\n<\/ol>\n\n\n\n<p>Examples that may exist (availability varies; <strong>verify in your region<\/strong>):\n&#8211; Developer-oriented images\n&#8211; Open-source runtime images\n&#8211; Tooling images<\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"4\">\n<li>Open the listing and read:\n   &#8211; <strong>Pricing<\/strong> section (ensure software fee is free for the lab)\n   &#8211; <strong>Support<\/strong> section\n   &#8211; <strong>Architecture\/deployment<\/strong> guidance\n   &#8211; <strong>Terms<\/strong> (what you\u2019re accepting)<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have selected a free image listing suitable for launching.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Confirm the listing indicates it can be launched as an image on Compute in your region.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Launch the Marketplace image as a Compute instance<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the listing page, click <strong>Get App<\/strong> \/ <strong>Launch Instance<\/strong> (button text varies).<\/li>\n<li>If prompted, <strong>accept terms and conditions<\/strong>.<\/li>\n<li>\n<p>In the launch workflow:\n   &#8211; <strong>Compartment:<\/strong> <code>cmp-mkt-lab<\/code>\n   &#8211; <strong>Instance name:<\/strong> <code>vm-mkt-lab-01<\/code>\n   &#8211; <strong>Availability domain\/fault domain:<\/strong> leave default\n   &#8211; <strong>Image:<\/strong> should be the Marketplace image you selected\n   &#8211; <strong>Shape:<\/strong> choose a small shape appropriate for labs (and Always Free-eligible where possible)\n   &#8211; <strong>Networking:<\/strong><\/p>\n<ul>\n<li>VCN: the lab VCN from Step 2<\/li>\n<li>Subnet: public subnet<\/li>\n<li>Assign a public IPv4 address: <strong>Yes<\/strong> (for simplest SSH; in production prefer Bastion\/private)<\/li>\n<li><strong>SSH keys:<\/strong><\/li>\n<li>Generate a new key pair (download private key) or paste your public key<\/li>\n<\/ul>\n<\/li>\n<li>\n<p>Click <strong>Create<\/strong> (or <strong>Launch<\/strong>).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Instance provisioning starts and eventually reaches <strong>Running<\/strong> state with a public IP.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Navigate to the instance details page:\n  &#8211; Lifecycle state: <strong>Running<\/strong>\n  &#8211; Public IPv4 address: present\n  &#8211; VNIC attached<\/p>\n\n\n\n<p><strong>Common issue:<\/strong> If the shape selection fails due to limits, check <strong>service limits\/quotas<\/strong> for Compute.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Configure SSH access from your workstation<\/h3>\n\n\n\n<p>On your machine, ensure the private key has correct permissions.<\/p>\n\n\n\n<pre><code class=\"language-bash\">chmod 600 ~\/Downloads\/ssh-key-2026-*.key\n<\/code><\/pre>\n\n\n\n<p>Identify:\n&#8211; <code>PUBLIC_IP<\/code> from the instance page\n&#8211; <code>SSH_USER<\/code> from listing documentation (this varies by image)<\/p>\n\n\n\n<p>Common usernames for OCI images include <code>opc<\/code> (but <strong>do not assume<\/strong>\u2014verify the listing details).<\/p>\n\n\n\n<p><strong>Connect:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">ssh -i ~\/Downloads\/ssh-key-2026-*.key &lt;SSH_USER&gt;@&lt;PUBLIC_IP&gt;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> You get a shell prompt on the VM.<\/p>\n\n\n\n<p><strong>Verification commands (run on the VM):<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">uname -a\ncat \/etc\/os-release\n<\/code><\/pre>\n\n\n\n<p>If the listing is supposed to have preinstalled software, verify per its docs (examples):<\/p>\n\n\n\n<pre><code class=\"language-bash\"># Examples only\u2014use commands relevant to your chosen listing\npython3 --version\ndocker --version\njava -version\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: (Optional) Verify network exposure is minimal<\/h3>\n\n\n\n<p>For a lab you might have opened SSH broadly. Confirm your security list\/NSG is not more permissive than needed.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to the instance \u2192 VNIC \u2192 Subnet \u2192 Security List (or NSG if used).<\/li>\n<li>Confirm inbound rules:\n   &#8211; SSH (TCP\/22) from <strong>your IP<\/strong> is preferred\n   &#8211; Avoid <code>0.0.0.0\/0<\/code> in production<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Inbound access is constrained.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; SSH remains accessible from your machine after tightening rules.<\/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>You have successfully used Oracle Cloud Marketplace to:\n&#8211; Select a listing\n&#8211; Accept terms\n&#8211; Launch a Marketplace image as a Compute instance\n&#8211; Connect to it and validate system status<\/p>\n\n\n\n<p><strong>Checklist:<\/strong>\n&#8211; Instance is Running\n&#8211; Public IP assigned (lab)\n&#8211; SSH works with your key\n&#8211; OS\/software matches the listing documentation<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p><strong>Issue: Instance fails to launch<\/strong>\n&#8211; Check <strong>service limits<\/strong> (Compute OCPUs, instances).\n&#8211; Try a smaller shape.\n&#8211; Ensure your chosen listing supports your region and shape type.<\/p>\n\n\n\n<p><strong>Issue: SSH connection times out<\/strong>\n&#8211; Confirm instance has a <strong>public IP<\/strong>.\n&#8211; Confirm subnet route table has <code>0.0.0.0\/0<\/code> to an Internet Gateway.\n&#8211; Confirm security list\/NSG allows inbound TCP\/22 from your source IP.\n&#8211; Confirm local firewall\/corporate network allows outbound SSH.<\/p>\n\n\n\n<p><strong>Issue: SSH \u201cPermission denied (publickey)\u201d<\/strong>\n&#8211; Verify you used the correct private key.\n&#8211; Verify the correct username from listing documentation.\n&#8211; Confirm the key you uploaded matches the private key you\u2019re using.<\/p>\n\n\n\n<p><strong>Issue: Unexpected charges<\/strong>\n&#8211; Verify whether the listing has a paid software component.\n&#8211; Ensure you terminate the instance and delete any load balancers or extra volumes created by templates.\n&#8211; Use <strong>cost analysis<\/strong> (OCI billing tools) and tags to identify resources.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges, clean up resources created by the lab.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Terminate the Compute instance<\/strong>\n   &#8211; Compute \u2192 Instances \u2192 <code>vm-mkt-lab-01<\/code> \u2192 <strong>Terminate<\/strong>\n   &#8211; Choose to delete attached boot volume (for full cleanup) unless you intentionally want to keep it<\/p>\n<\/li>\n<li>\n<p><strong>Delete the VCN<\/strong>\n   &#8211; Networking \u2192 VCNs \u2192 select your lab VCN \u2192 <strong>Terminate<\/strong>\n   &#8211; If deletion fails, remove dependent resources first (instances, gateways, route rules, subnets)<\/p>\n<\/li>\n<li>\n<p><strong>Delete the compartment<\/strong> (optional; only if it contains no resources)\n   &#8211; Identity \u2192 Compartments \u2192 <code>cmp-mkt-lab<\/code> \u2192 <strong>Delete<\/strong><\/p>\n<\/li>\n<li>\n<p><strong>Review for leftovers<\/strong>\n   &#8211; Check for block volumes, public IPs, load balancers, NAT gateways, etc.<\/p>\n<\/li>\n<\/ol>\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 (IaC) deployments<\/strong> for repeatability and auditability.<\/li>\n<li>Use a <strong>landing zone<\/strong> approach:<\/li>\n<li>Separate compartments for network, shared services, and applications<\/li>\n<li>Dedicated subnets for management vs application traffic<\/li>\n<li>For production, design for:<\/li>\n<li>Multi-fault-domain deployments (where applicable)<\/li>\n<li>Load balancers and health checks<\/li>\n<li>Backup and restore workflows<\/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 least privilege:<\/li>\n<li>Separate \u201cMarketplace subscription\u201d rights from \u201cresource creation\u201d rights if your process requires approvals.<\/li>\n<li>Use compartments to constrain blast radius.<\/li>\n<li>Require MFA and federated identity where possible.<\/li>\n<li>Restrict who can accept Marketplace terms (procurement\/legal alignment).<\/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>Tag every Marketplace-deployed resource with:<\/li>\n<li><code>CostCenter<\/code>, <code>Environment<\/code>, <code>Application<\/code>, <code>Owner<\/code><\/li>\n<li>Prefer minimal shapes in dev\/test and schedule shutdowns.<\/li>\n<li>Review stack templates to understand what billable resources will be created before deploying.<\/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>Validate sizing guidance from the listing and benchmark with your workload.<\/li>\n<li>Ensure network design matches throughput requirements (LB shape, subnet design, NSG rules).<\/li>\n<li>Avoid over-provisioning early; scale based on metrics.<\/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>Use multiple instances and health checks for critical components.<\/li>\n<li>Store configuration in code (Git), not only in manual console settings.<\/li>\n<li>Plan for patch windows and upgrades (publisher images do not automatically keep you safe).<\/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>Integrate with OCI Monitoring, Logging, and Alerts from day one.<\/li>\n<li>Use OS Management (where appropriate) or your standard patch toolchain (verify current OCI OS management options).<\/li>\n<li>Document:<\/li>\n<li>What was deployed (listing version, parameters)<\/li>\n<li>How it\u2019s supported (vendor vs internal)<\/li>\n<li>How to restore\/recreate (runbooks)<\/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>Naming conventions:<\/li>\n<li><code>env-app-component-region-##<\/code> (example: <code>prod-payments-fw-phx-01<\/code>)<\/li>\n<li>Use tag defaults at compartment level where possible.<\/li>\n<li>Treat Marketplace deployments as code:<\/li>\n<li>Store inputs\/parameters<\/li>\n<li>Store version references<\/li>\n<li>Require peer review for production<\/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>Marketplace actions are governed by <strong>OCI IAM<\/strong>.<\/li>\n<li>Control who can:<\/li>\n<li>Browse listings (read-only)<\/li>\n<li>Accept terms\/subscribe<\/li>\n<li>Deploy resources (create\/modify Compute\/Network\/etc.)<\/li>\n<li>Use compartment scoping to prevent accidental production deployments.<\/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 resources such as block volumes support encryption by default (verify current defaults and options in official docs).<\/li>\n<li>For application-level secrets:<\/li>\n<li>Use <strong>OCI Vault<\/strong> for keys and secrets<\/li>\n<li>Avoid embedding secrets in cloud-init or Terraform variables in plain text<\/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>Avoid public IPs in production unless required.<\/li>\n<li>Use <strong>OCI Bastion<\/strong> for SSH\/RDP access patterns.<\/li>\n<li>Place appliances in dedicated subnets and restrict east-west movement with NSGs and route controls.<\/li>\n<li>Consider <strong>WAF<\/strong> and <strong>Load Balancer<\/strong> for public web exposure.<\/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 store passwords\/API keys in:<\/li>\n<li>User-data scripts<\/li>\n<li>Git repositories<\/li>\n<li>Instance metadata in plaintext<\/li>\n<li>Use Vault and instance principals (where supported) for OCI API access patterns.<\/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>Ensure <strong>OCI Audit<\/strong> is enabled and monitored (Audit is generally enabled by default; verify retention and access).<\/li>\n<li>Forward critical logs to a central logging system; restrict who can disable logging.<\/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>Validate:<\/li>\n<li>Publisher claims (certifications, compliance) directly in official listing docs and vendor sites.<\/li>\n<li>Data residency and region requirements.<\/li>\n<li>Keep an inventory of:<\/li>\n<li>Marketplace listing name\/version<\/li>\n<li>Deployed software versions<\/li>\n<li>Patch status and exceptions<\/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>Deploying from unknown publishers without validation<\/li>\n<li>Leaving SSH open to the internet (<code>0.0.0.0\/0<\/code>)<\/li>\n<li>Forgetting to patch images and dependencies<\/li>\n<li>Accepting terms\/licensing without procurement review<\/li>\n<li>Not scanning instances for vulnerabilities post-deploy<\/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>Use private subnets + Bastion where possible.<\/li>\n<li>Apply NSGs with least-privilege ports.<\/li>\n<li>Enable monitoring and alerting immediately.<\/li>\n<li>For stacks, review Terraform code before applying:<\/li>\n<li>Look for overly permissive security rules<\/li>\n<li>Validate IAM policies created by templates<\/li>\n<li>Confirm no unexpected public endpoints<\/li>\n<\/ul>\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> A solution you see in one region may not be deployable in another.<\/li>\n<li><strong>\u201cFree listing\u201d does not mean \u201cfree deployment.\u201d<\/strong> Compute, storage, load balancer, and egress can still cost money.<\/li>\n<li><strong>Publisher support boundaries:<\/strong> Oracle supports OCI infrastructure; publishers support their software\u2014unless explicitly stated otherwise.<\/li>\n<li><strong>Image drift:<\/strong> Marketplace images may become outdated if you don\u2019t patch after deployment.<\/li>\n<li><strong>Stacks can create many resources quickly:<\/strong> including expensive components. Always review the template and planned resources before deploying.<\/li>\n<li><strong>IAM complexity:<\/strong> Marketplace subscriptions + resource creation may require multiple policy permissions.<\/li>\n<li><strong>Network defaults may be insecure:<\/strong> some templates open broad ingress for convenience; tighten for production.<\/li>\n<li><strong>Upgrades are on you:<\/strong> launching an image is not the same as managed service upgrades.<\/li>\n<li><strong>Compatibility constraints:<\/strong> certain images may require specific shapes, CPU architectures, or OS versions.<\/li>\n<li><strong>Termination doesn\u2019t always delete everything:<\/strong> stacks may leave behind volumes, public IPs, or buckets; validate cleanup.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">How Using Marketplace compares<\/h3>\n\n\n\n<p>Using Marketplace is best viewed as \u201csolution acquisition + deployment integration\u201d. Alternatives vary depending on what you\u2019re trying to achieve.<\/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 Using Marketplace (OCI Marketplace)<\/strong><\/td>\n<td>Deploying partner\/Oracle solutions into OCI with terms + optional integrated billing<\/td>\n<td>Integrated with OCI IAM\/compartments; images and stacks; supports multiple pricing models<\/td>\n<td>Listing availability varies; quality varies by publisher; you still operate the runtime<\/td>\n<td>When you need vendor solutions deployed into OCI quickly with governance<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Compute custom images \/ golden images<\/strong><\/td>\n<td>Standard internal images with consistent hardening<\/td>\n<td>Full control; consistent baseline; integrates with your CI image pipeline<\/td>\n<td>Requires you to build\/maintain images and software<\/td>\n<td>When you have strict security baselines or need internal standardization<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Resource Manager (direct Terraform, not via Marketplace)<\/strong><\/td>\n<td>Infrastructure as code for OCI without Marketplace catalog<\/td>\n<td>Full flexibility; version-controlled modules<\/td>\n<td>No catalog discovery; more work to build templates<\/td>\n<td>When you already have Terraform modules and want full control<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Marketplace<\/strong><\/td>\n<td>Similar marketplace flow on AWS<\/td>\n<td>Broad ecosystem; tight integration with AWS services<\/td>\n<td>Different IAM\/networking model; not OCI<\/td>\n<td>Choose if your workloads run primarily on AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Marketplace<\/strong><\/td>\n<td>Similar on Microsoft Azure<\/td>\n<td>Strong enterprise procurement integrations<\/td>\n<td>Not OCI; different deployment constructs<\/td>\n<td>Choose if your workloads run primarily on Azure<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Marketplace<\/strong><\/td>\n<td>Similar on Google Cloud<\/td>\n<td>Integrated with GCP deployment patterns<\/td>\n<td>Not OCI; different constructs<\/td>\n<td>Choose if your workloads run primarily on GCP<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed installs from vendor repos<\/strong><\/td>\n<td>Maximum control, minimal marketplace coupling<\/td>\n<td>No marketplace constraints; fully customizable<\/td>\n<td>Higher setup time; more integration effort; licensing procurement is manual<\/td>\n<td>When Marketplace doesn\u2019t offer what you need or you require custom builds<\/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: Shared security services rollout<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A financial enterprise needs to standardize a network security appliance across multiple application teams. Teams currently deploy ad-hoc solutions with inconsistent configurations.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>A dedicated <strong>Shared Services<\/strong> compartment<\/li>\n<li>Hub VCN with dedicated subnets for security appliances<\/li>\n<li>Marketplace image deployment of the vendor appliance (two instances for HA where supported)<\/li>\n<li>Spoke VCNs for application teams with controlled routing through the hub<\/li>\n<li>Centralized logging to OCI Logging (and\/or external SIEM)<\/li>\n<li><strong>Why Using Marketplace was chosen:<\/strong><\/li>\n<li>Official vendor-provided image and documented OCI deployment pattern<\/li>\n<li>Clear support boundaries and licensing approach<\/li>\n<li>Repeatable deployment with consistent versions<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Faster onboarding for new application VCNs<\/li>\n<li>Improved audit posture via standard deployment and OCI Audit logs<\/li>\n<li>Reduced risk from inconsistent firewall deployments<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: Quick POC environment for a customer demo<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A startup needs to demo a secure web app architecture to a customer within a week, without spending days on manual setup.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>One compartment for demo<\/li>\n<li>VCN + public subnet (lab) or private subnet + Bastion (more secure)<\/li>\n<li>Marketplace image for a preconfigured reverse proxy or app runtime (listing-dependent)<\/li>\n<li>Basic alarms and logging<\/li>\n<li><strong>Why Using Marketplace was chosen:<\/strong><\/li>\n<li>Speed: deploy a working environment in hours<\/li>\n<li>Lower complexity than assembling components manually<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Repeatable demo environments<\/li>\n<li>Easy teardown to control costs<\/li>\n<li>Faster iteration during customer feedback cycles<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is \u201cUsing Marketplace\u201d a separate billable Oracle Cloud service?<\/strong><br\/>\nNot typically. Marketplace is a catalog and deployment integration. Costs come from (a) OCI resources you deploy and (b) listing-specific software charges if the publisher bills through OCI. Always check the listing pricing and OCI billing.<\/p>\n\n\n\n<p>2) <strong>Do I need a paid account to use Marketplace?<\/strong><br\/>\nYou need a valid tenancy and the ability to provision underlying resources. Even for free listings, resource provisioning may require a billing-enabled account. Verify current account requirements and Always Free eligibility.<\/p>\n\n\n\n<p>3) <strong>Can I deploy Marketplace images into private subnets?<\/strong><br\/>\nYes, in many cases. You must ensure the instance can reach required update repositories or license endpoints (via NAT Gateway, Service Gateway, or private connectivity), and you must provide a secure access pattern (Bastion, VPN).<\/p>\n\n\n\n<p>4) <strong>How do I know if a listing is safe?<\/strong><br\/>\nCheck publisher identity, documentation quality, update cadence, support model, and community\/vendor reputation. For production, perform security reviews: scan the instance, review open ports, and validate configuration.<\/p>\n\n\n\n<p>5) <strong>Who supports the software: Oracle or the publisher?<\/strong><br\/>\nUsually the publisher supports their software; Oracle supports OCI infrastructure. Some listings might have different arrangements\u2014verify the listing\u2019s support section.<\/p>\n\n\n\n<p>6) <strong>Can Marketplace stacks create IAM policies automatically?<\/strong><br\/>\nSome stacks may create IAM resources if designed to. Treat this as high risk: review Terraform before applying and use least privilege.<\/p>\n\n\n\n<p>7) <strong>What happens if I terminate a VM launched from a Marketplace image?<\/strong><br\/>\nThe VM stops existing, but attached resources (boot volume, block volumes, public IPs) may remain depending on your termination options and template behavior.<\/p>\n\n\n\n<p>8) <strong>Can I automate Marketplace deployments with CI\/CD?<\/strong><br\/>\nOften yes, especially with stack-based deployments (Terraform\/Resource Manager). The exact automation path depends on the listing and OCI APIs. Verify current supported automation methods in OCI docs.<\/p>\n\n\n\n<p>9) <strong>Are Marketplace images updated automatically after I launch them?<\/strong><br\/>\nNo. Once launched, it\u2019s your responsibility to patch and maintain the instance unless you use a managed service or automation tooling.<\/p>\n\n\n\n<p>10) <strong>Can I restrict which listings my organization can deploy?<\/strong><br\/>\nYou can restrict who can deploy by IAM and compartments, and you can build internal controls (approvals, curated processes). The exact mechanisms for \u201callowlisting listings\u201d should be verified in official docs and your governance tooling.<\/p>\n\n\n\n<p>11) <strong>Why can\u2019t I find a listing that someone else sees?<\/strong><br\/>\nCommon reasons: region differences, tenancy restrictions, listing retired\/updated, or publisher availability constraints.<\/p>\n\n\n\n<p>12) <strong>Do Marketplace deployments work with ARM-based shapes and different CPU architectures?<\/strong><br\/>\nSome images support specific architectures only. Check listing requirements and supported shapes.<\/p>\n\n\n\n<p>13) <strong>How do I estimate cost before deploying a listing?<\/strong><br\/>\nIdentify resources the deployment will create (compute, storage, LB, NAT, etc.) and use the OCI cost estimator. For paid listings, include publisher fees described in the listing.<\/p>\n\n\n\n<p>14) <strong>Can I use my own SSH keys and hardening standards with Marketplace images?<\/strong><br\/>\nYes. You generally provide your SSH keys during instance launch and can apply your standard hardening after deployment (CIS baselines, agent installs, etc.).<\/p>\n\n\n\n<p>15) <strong>What\u2019s the best practice for production: image or stack?<\/strong><br\/>\nFor production, stacks (IaC) often provide better repeatability and auditability. Images can still be appropriate, but you should wrap them in IaC and operational controls.<\/p>\n\n\n\n<p>16) <strong>Can I migrate a Marketplace deployment between regions?<\/strong><br\/>\nNot directly. You typically redeploy in the target region and migrate data\/configuration using standard methods. Validate licensing terms for multi-region usage.<\/p>\n\n\n\n<p>17) <strong>What should I document for compliance?<\/strong><br\/>\nAt minimum: listing name\/version, publisher, pricing model, acceptance of terms, deployment parameters, network exposure, patching policy, support contacts, and audit logs retention.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Using Marketplace<\/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>OCI Marketplace docs<\/td>\n<td>Canonical reference for Marketplace concepts and workflows: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Marketplace\/home.htm<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI IAM docs<\/td>\n<td>Required to design permissions safely: 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>Important for stack-based Marketplace deployments: 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 price list<\/td>\n<td>Understand baseline OCI service pricing: https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<\/tr>\n<tr>\n<td>Official pricing tool<\/td>\n<td>OCI Cost Estimator<\/td>\n<td>Model costs before deployment: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<\/tr>\n<tr>\n<td>Official Free Tier<\/td>\n<td>Oracle Cloud Free Tier<\/td>\n<td>Always Free eligibility and limits: https:\/\/www.oracle.com\/cloud\/free\/<\/td>\n<\/tr>\n<tr>\n<td>Architecture center<\/td>\n<td>Oracle Architecture Center \/ Solutions<\/td>\n<td>Reference architectures and patterns: https:\/\/docs.oracle.com\/en\/solutions\/<\/td>\n<\/tr>\n<tr>\n<td>Official tutorials<\/td>\n<td>Oracle Cloud \u201cLearn\u201d<\/td>\n<td>Guided labs and tutorials (search for Marketplace\/Resource Manager): https:\/\/docs.oracle.com\/en\/learn\/<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle Cloud YouTube channel<\/td>\n<td>Product walkthroughs and demos; search Marketplace: https:\/\/www.youtube.com\/@OracleCloudInfrastructure<\/td>\n<\/tr>\n<tr>\n<td>Samples (trusted)<\/td>\n<td>Oracle GitHub org<\/td>\n<td>IaC samples and reference code (verify Marketplace relevance per repo): https:\/\/github.com\/oracle<\/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<p>The following training providers may offer Oracle Cloud, DevOps, and cloud marketplace-related learning. Verify current course availability and delivery modes on each website.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, cloud engineers<\/td>\n<td>DevOps practices, cloud automation, IaC fundamentals<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate DevOps learners<\/td>\n<td>SCM, CI\/CD, DevOps tooling basics<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud operations teams<\/td>\n<td>Cloud ops, monitoring, reliability practices<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, platform engineers<\/td>\n<td>SRE principles, incident response, reliability engineering<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops teams exploring AIOps<\/td>\n<td>AIOps concepts, automation, operational analytics<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>These sites may provide trainer profiles, training services, or learning resources. Verify background, curriculum, and Oracle Cloud coverage directly.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training content<\/td>\n<td>Students, engineers seeking guided learning<\/td>\n<td>https:\/\/www.rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps coaching\/training<\/td>\n<td>DevOps engineers, CI\/CD practitioners<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps support\/training<\/td>\n<td>Small teams needing hands-on help<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>Operational support and training resources<\/td>\n<td>Ops teams, DevOps teams<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>These organizations may offer consulting for DevOps, cloud adoption, automation, and operations. Validate OCI Marketplace-specific experience during vendor selection.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting<\/td>\n<td>Architecture, automation, deployments<\/td>\n<td>Marketplace-based deployment standardization; IaC rollout; ops runbooks<\/td>\n<td>https:\/\/www.cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps consulting &amp; training<\/td>\n<td>DevOps transformation, CI\/CD, tooling<\/td>\n<td>Building deployment pipelines for Marketplace stacks; governance and tagging strategy<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting<\/td>\n<td>DevOps implementation and support<\/td>\n<td>Production hardening of Marketplace images; monitoring\/logging integration<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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 Using Marketplace<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI fundamentals:<\/li>\n<li>Tenancy, compartments, regions<\/li>\n<li>VCN basics (subnets, routing, gateways, NSGs)<\/li>\n<li>Compute basics (instances, shapes, boot volumes)<\/li>\n<li>IAM:<\/li>\n<li>Users, groups, policies, least privilege<\/li>\n<li>Basic Linux administration:<\/li>\n<li>SSH, firewall concepts, package management<\/li>\n<li>Cost basics:<\/li>\n<li>How OCI charges for compute\/storage\/egress<\/li>\n<li>Tagging and budgeting concepts<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Using Marketplace<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Infrastructure as Code:<\/li>\n<li>Terraform fundamentals<\/li>\n<li>OCI Resource Manager workflows<\/li>\n<li>Production networking patterns:<\/li>\n<li>Hub-and-spoke, private subnets, bastion, load balancers<\/li>\n<li>Observability:<\/li>\n<li>OCI Monitoring, Logging, alarms, dashboards<\/li>\n<li>Security hardening:<\/li>\n<li>Vulnerability scanning, patching, secrets management (Vault)<\/li>\n<li>Governance:<\/li>\n<li>Policy-as-code, change management, release pipelines<\/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 administrator<\/li>\n<li>Solutions architect<\/li>\n<li>DevOps engineer \/ platform engineer<\/li>\n<li>SRE<\/li>\n<li>Security engineer (especially for appliance deployments)<\/li>\n<li>FinOps analyst (tracking and optimizing Marketplace-related spend)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle Cloud certifications change over time. Use Oracle University for the latest certification tracks and exam codes (verify current paths):\nhttps:\/\/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 a \u201ccurated Marketplace deployment\u201d pipeline:<\/li>\n<li>Approved listing \u2192 IaC stack \u2192 private subnet deployment \u2192 monitoring + alerts<\/li>\n<li>Create a cost dashboard for Marketplace deployments using tags.<\/li>\n<li>Design a multi-environment pattern (dev\/stage\/prod) with compartment separation and policy boundaries.<\/li>\n<li>Build a hardened VM baseline process for Marketplace images (post-launch hardening scripts + CIS checks).<\/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>Oracle Cloud (OCI):<\/strong> Oracle Cloud Infrastructure, the IaaS platform where Marketplace deployments run.<\/li>\n<li><strong>Marketplace:<\/strong> Oracle Cloud Marketplace catalog of partner\/Oracle solutions.<\/li>\n<li><strong>Using Marketplace:<\/strong> The workflow of discovering, subscribing, and deploying Marketplace listings into your OCI tenancy.<\/li>\n<li><strong>Listing:<\/strong> A catalog entry in Marketplace describing a solution, its artifacts, pricing, and support.<\/li>\n<li><strong>Publisher:<\/strong> The vendor or organization that provides the listing.<\/li>\n<li><strong>Image (Marketplace image):<\/strong> A VM image used to launch a Compute instance with preinstalled software.<\/li>\n<li><strong>Stack:<\/strong> A deployable IaC template (commonly Terraform) that provisions multiple OCI resources.<\/li>\n<li><strong>OCI Resource Manager:<\/strong> OCI service that runs Terraform to provision resources.<\/li>\n<li><strong>Tenancy:<\/strong> Your top-level OCI account boundary.<\/li>\n<li><strong>Compartment:<\/strong> A logical isolation boundary inside a tenancy for organizing and controlling access to resources.<\/li>\n<li><strong>IAM Policy:<\/strong> Rules that define who can do what to which resources in OCI.<\/li>\n<li><strong>BYOL:<\/strong> Bring Your Own License; you supply an existing software license.<\/li>\n<li><strong>Metered billing:<\/strong> Usage-based billing, often hourly or by consumption units, depending on the listing.<\/li>\n<li><strong>VCN:<\/strong> Virtual Cloud Network, OCI\u2019s virtual networking construct.<\/li>\n<li><strong>NSG:<\/strong> Network Security Group, used to apply security rules to VNICs.<\/li>\n<li><strong>Internet Gateway \/ NAT Gateway:<\/strong> VCN components providing internet connectivity (inbound\/outbound patterns differ).<\/li>\n<li><strong>OCI Audit:<\/strong> Service that records API calls and actions for governance and security investigations.<\/li>\n<li><strong>OCPU:<\/strong> Oracle CPU unit used in OCI compute sizing (pricing and meaning can vary by shape type; verify current definitions in OCI docs).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Using Marketplace in <strong>Oracle Cloud<\/strong> is the disciplined way to <strong>find, evaluate, subscribe to, and deploy<\/strong> Marketplace solutions into your OCI tenancy. It matters because it shortens delivery timelines, supports repeatable deployments (especially with stacks), and provides a governed path to adopt vendor software while staying inside OCI\u2019s IAM and compartment model.<\/p>\n\n\n\n<p>Cost-wise, Marketplace is not \u201cautomatically free\u201d\u2014you pay for the OCI resources you deploy, and some listings add publisher software charges depending on licensing and billing model. Security-wise, treat Marketplace artifacts like any supply-chain input: validate publishers, review templates, restrict network exposure, and establish patching and monitoring from day one.<\/p>\n\n\n\n<p>Use Using Marketplace when you need fast, standardized deployments of vendor solutions with clear terms and operational integration into OCI. Next, deepen your skills with <strong>OCI Resource Manager (Terraform)<\/strong> and production governance (IAM, tagging, monitoring, and security hardening) so Marketplace deployments remain safe, repeatable, and cost-controlled.<\/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-930","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\/930","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=930"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/930\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}