Oracle Cloud Infrastructure Documentation

New Partners

All publisher activities must now take place in the OCI Console using Console Publishing.

Use this topic to onboard as a partner, confirm tenancy readiness, access Marketplace Publisher, and create the required tenancy policies.

Partner Onboarding and Tenancy Readiness

Onboard as a partner and confirm that the tenancy is ready for Marketplace publishing.

  1. Onboard to become a partner by following the steps outlined here: https://cloudmarketplace.oracle.com/marketplace/en_US/partnerLandingPage.

  2. Confirm OCI tenancy readiness.

    • When creating the tenancy, we recommend choosing US East (Ashburn) as the home region. If you choose a different home region, the tenancy must still be subscribed to US East (Ashburn). To create or edit Publisher resources, select US East (Ashburn) in the Console (the Publisher service is available only in this region).
    • Select the US East (Ashburn) region to manage listings in Console. You can subscribe to US East (Ashburn) by following these steps.
    • Paid or PAYG tenancy is recommended to avoid trial expiration interruptions. No charges are incurred unless you use billable services. See Marketplace Publisher FAQ.
    • Add Marketplace policies using the Deploy to Oracle Cloud workflow in OCI Marketplace Setup Github. OCI Marketplace Setup is a Resource Manager/Terraform quickstart that sets up Marketplace publishing IAM foundations including groups and policies in the tenancy. After deployment, OCI Marketplace Setup creates service access for Marketplace artifacts and admin roles for publisher and private offer workflows but doesn't create users or add users to groups. See the following:

Access Marketplace Publisher in the Console

Access Marketplace Publisher and select the compartment for listing creation.

  1. Access Marketplace Publisher in the Console.
  2. Open the navigation menu  and select Marketplace. Under Publisher, select Listings..
  3. Select the compartment where you want to create Marketplace listings.
  4. To create a lead generation (Application Listing), follow the steps Creating a Lead Generation Listing.
  5. To create a OCI Application listing with a deployable artifact including images, containers or stacks, follow the steps Creating an OCI Application Listing.
  6. To create a Service listing, follow the steps Creating a Service Listing.

Create a Policy for Package Listings in an OCI Tenancy

Create policies in the tenancy for package listings that use Marketplace artifacts such as images, stacks, containers, helm charts, or deployable resources.

To create a policy for an OCI tenancy, follow these steps:

  1. Sign in to the OCI Console.
  2. From the main navigation menu , select Identity & Security. Under Identity, select Policies.
  3. For Compartment, select the root compartment.
  4. Select Create Policy.
  5. Fill out the details in the Create Policy form.
    1. Name: Enter a name for the policy. For example, Marketplace-Service-Policy.
    2. Description: Enter a description for the policy.
    3. Policy Versioning: Select the KEEP POLICY CURRENT option.
    4. Policy Statements: Add the following policy statements:
      • ALLOW SERVICE marketplace to manage App-catalog-publisher-listing IN TENANCY
      • ALLOW SERVICE marketplace to read tenant IN TENANCY
      • ALLOW SERVICE marketplace to read compartments IN TENANCY
      • ALLOW SERVICE marketplace to read instance-images IN TENANCY
      • ALLOW SERVICE marketplace to inspect instances IN TENANCY
      • ALLOW SERVICE marketplace to read orm-stacks IN TENANCY (new policy required for stack validation)
      • ALLOW SERVICE marketplace to read orm-jobs IN TENANCY (new policy required for stack validation)
  6. Select Create.
Note

These package-specific policies aren't required for Lead Generation or AI Agent listings unless those listings include package artifacts or deployment resources.

IAM policy is required for all listing types, but package listings require the additional package/artifact policies described in this section.

See also: Required IAM Policy.