Reference

Cloud marketplace resources for software vendors

53 references for publishing and selling through the Azure, AWS and Google Cloud marketplaces — registration, image requirements, certification, fees, private offers, tooling and the feeds worth tracking.

Every link was fetched and confirmed to resolve on 31 October 2026, and each description reflects what the page says rather than what its title implies. Two things that cost us time while checking, in case they save you some: a number of plausible AWS Marketplace documentation URLs return HTTP 200 while serving an empty shell with no content, so a status-code check passes them — and Microsoft has reorganised its marketplace paths, so slugs that look correct frequently 404.

Becoming a publisher

Where each cloud actually starts you, which is not always the page you would guess. Microsoft has no single standalone 'register as a marketplace publisher' document — the overview and the publishing guide are the real entry points, and the similarly named developer-account page is Office-store oriented.

Image and product technical requirements

What the artefact itself has to satisfy. These are the pages that determine whether a build passes or bounces, and they are the ones worth reading in full before writing any Packer configuration.

Certification, scanning and submission

The review gate between a finished image and a live listing. None of the three clouds publishes a certification turnaround time — if you find a number quoted anywhere, it did not come from vendor documentation.

Listing content and version updates

Publishing once is the easy part. Shipping version two against a live listing is where most of the ongoing operational cost lives, and it is the least collected topic in this entire space.

Fees, private offers and commitment drawdown

The commercial mechanics, and the place where the three clouds differ most in what they are willing to tell you. Microsoft publishes both its fee rate and its commitment drawdown clearly; AWS publishes an exhaustive fee schedule but no drawdown percentage; Google publishes neither.

Build and automation tooling

What teams actually use to build images and automate submission. Each cloud exposes an API for publishing, which is what turns listing maintenance from manual portal work into a pipeline.

Hardening and compliance baselines

Marketplace scanning checks that an image is not obviously vulnerable; it does not make it hardened. These are the baselines teams build against when a buyer asks what standard an image meets.

Tracking changes

Marketplace rules change without much ceremony, and fee schedules in particular have moved more than once in the past two years. These are the feeds worth watching.

Independent analysis and market data

This is the thinnest category by a wide margin, and that is a finding rather than an omission. We searched specifically for a marketplace-seller community — Slack, Discord, forum — and found none. The general partner communities exist but are not marketplace-specific.

Why this list exists

There was no maintained, vendor-neutral reference for selling through the cloud marketplaces. We looked for one specifically — a curated resource page, an awesome-list, a community wiki — and found nothing. What exists is scattered across three vendors’ documentation sets, each organised around its own products rather than around the job of publishing and selling.

WIEWAVE builds, hardens, certifies and maintains marketplace images across all three clouds, so this list is the one we needed ourselves. It links to the primary documentation rather than restating it, flags where a vendor publishes nothing, and says plainly when a resource is self-interested or licence-restricted. If something here has gone stale or you know of a resource that belongs, tell us and we will check it.

Publishing to a cloud marketplace?

We build, harden, certify and maintain marketplace images across Azure, AWS and Google Cloud — tell us what you're listing.

Start a conversation Email us directly