AWS Marketplace is Amazon’s catalogue of third-party software that runs on AWS,
billed through your existing AWS relationship rather than through separate vendor
contracts. If you want to buy AWS Marketplace account access, this page
lists two configurations, at $90 and $750.
Overview: what AWS Marketplace is for
The problem AWS Marketplace solves is procurement friction. Deploying a commercial
security appliance, database engine or monitoring product traditionally means a separate
vendor negotiation, a separate contract, a separate invoice and a separate licence key.
Marketplace collapses that: software is selected from a catalogue, deployed into your
account, and billed on the same AWS invoice as everything else.
For organisations with established AWS spend and procurement processes, that
consolidation is the entire value proposition. AWS documents the service in the
AWS Marketplace documentation.
Available AWS Marketplace configurations
The table below is the complete list. Read it as the menu you choose from when you buy AWS Marketplace account configurations on this page — each row is priced and specified independently, so nothing is bundled or assumed.
| Configuration | Price |
|---|---|
| Verified Marketplace Account | $90 |
Both configurations describe an account state. Neither states entitlements to any
particular software, seller status, or any specific commercial terms — those are
governed by AWS and by individual software vendors. Confirm anything your project depends
on before ordering, via the contact page.
Key features
The points below summarise what distinguishes these options for anyone about to buy AWS Marketplace account configurations for the first time.
- Consolidated billing for third-party software on the AWS invoice.
- Several delivery methods — AMIs, containers, SaaS and machine learning models.
- Flexible pricing models including hourly, annual, and bring-your-own-licence.
- Private Offers for negotiated terms with individual sellers.
- Integration with AWS accounts and organisations for controlled procurement.
How software is delivered
Amazon Machine Images
The most common form. The vendor packages their software into an AMI, and you launch
an EC2 instance from it. Software charges are added to the instance’s hourly rate, so
there is nothing separate to install or license.
Container products
Images delivered for ECS, EKS or Kubernetes generally, suiting teams whose deployment
model is already containerised.
SaaS subscriptions
Software that runs on the vendor’s infrastructure rather than yours, with the
subscription procured and billed through Marketplace. You get the billing consolidation
without operating anything.
Machine learning models and data products
Pre-trained models deployable through SageMaker, and data sets available through AWS
Data Exchange. Useful where building or sourcing equivalents internally would be slower
than buying.
Professional services
Consulting and implementation engagements listed and billed through the same channel,
which brings services procurement into the same process as software.
Pricing models you will encounter
- Hourly — software charges added to instance runtime, with no commitment.
- Annual subscription — a fixed term, usually at a lower effective rate than hourly.
- Bring your own licence — you hold the licence already and Marketplace handles deployment only.
- Usage-based — billed on a vendor-defined metric such as data processed or endpoints monitored.
- Free and open-source listings — packaged for convenient deployment at no software cost.
Who these configurations suit
- Teams procuring third-party software to run on AWS — Verified Marketplace Account ($90).
- Organisations consolidating software spend onto an existing AWS invoice.
- Buyers who need negotiated commercial terms through Private Offers.
- Teams evaluating several commercial products quickly without separate vendor onboarding for each.
Common use cases
Security and compliance tooling
Firewalls, intrusion detection, vulnerability scanning and compliance monitoring are
among the most-purchased Marketplace categories, because they are exactly the products
organisations need quickly and do not want to build.
Databases and data infrastructure
Commercial database engines, analytics platforms and integration tooling deployed
directly into your own VPC, with licensing handled through the same billing relationship.
Developer and operations tooling
Monitoring, logging, CI/CD and observability products, deployed either as AMIs into
your account or subscribed as SaaS.
Rapid evaluation
Because hourly-billed products can be launched and destroyed freely, Marketplace is an
efficient way to trial several competing products properly rather than relying on vendor
demonstrations.
Machine learning acceleration
Deploying a pre-trained model through SageMaker where the alternative is training an
equivalent from scratch.
Procurement and governance considerations
Cost visibility
Marketplace charges appear on the AWS bill, which is convenient but can obscure
software spend inside overall infrastructure cost. Tagging Marketplace resources and
reviewing the Marketplace section of Cost Explorer separately keeps software spend
visible to whoever is accountable for it.
Controlling who can subscribe
Because subscribing commits real money, most organisations restrict it. IAM policies
can limit which principals may subscribe, and in AWS Organizations, service control
policies can enforce that centrally. Deciding this before the first subscription is
easier than discovering unexpected charges afterwards.
Private Offers
Public listing prices are not always the final word. Private Offers let a seller extend
custom pricing and terms to a specific buyer, which is how larger commitments are usually
transacted. If you are buying at any scale, the listed price is a starting point rather
than a fixed cost.
Contract terms come from the seller
Each listing carries its own end user licence agreement, support commitments and data
handling terms. AWS provides the billing and delivery channel; it does not standardise
what the vendor promises. Read the terms attached to the specific product rather than
assuming a uniform standard.
How Marketplace fits into an AWS estate
Marketplace is rarely used in isolation. Understanding how it interacts with the rest
of an AWS setup avoids both governance surprises and duplicated spend.
Accounts and organisations
In a multi-account AWS Organization, subscriptions are made from a specific account
and, depending on the product, can be shared across the organisation. Deciding early
whether procurement is centralised in a dedicated account or distributed to teams shapes
both cost visibility and who can commit money. Centralising is usually easier to control;
distributing is usually faster for teams.
Infrastructure cost sits underneath
An AMI-based product runs on EC2 instances you pay for separately. It is common for
the infrastructure to cost more than the software licence, particularly for products that
recommend generously sized instances. Model both together rather than evaluating the
listing price alone.
Build, buy, or use the AWS-native service
Before subscribing, it is worth asking whether AWS already offers a native equivalent.
Many Marketplace categories — monitoring, security, logging — overlap with AWS
services such as CloudWatch, GuardDuty and Security Hub. The third-party product is often
more capable or more familiar to the team, but the comparison should be deliberate rather
than skipped.
Trials and evaluation
Many listings offer free trial periods, and hourly-billed products can simply be run
briefly and destroyed. This makes genuine head-to-head evaluation practical in a way that
traditional procurement rarely allows — deploy two competing products into a test
account, run them against the same workload, and decide on evidence.
Practical guidance for buyers
Read the listing carefully
Listings vary considerably in quality and specificity. The details worth checking
before subscribing are the pricing dimension the vendor bills on, what support is
included, which instance types the product is certified for, and what the end user licence
agreement actually commits you to. A product billed per monitored endpoint behaves very
differently at scale from one billed per hour.
Watch the pricing dimension
Usage-based products define their own metric, and the metric determines how cost scales.
Per-hour scales with runtime, per-endpoint scales with your estate, per-gigabyte scales
with data. Matching the dimension to how your usage will actually grow is the difference
between predictable and alarming bills.
Plan the exit as well as the entry
Before committing to an annual subscription, understand what leaving looks like: can
data be exported, does the configuration transfer, and what happens to running workloads
at term end. Procurement that is easy to enter and hard to leave is a familiar trap, and
consolidated billing does not change it.
Deploying and operating Marketplace software
Subscribing is only the start. What happens afterwards varies considerably by delivery
method, and knowing the differences avoids unpleasant surprises during a rollout.
AMI-based products
Subscribing entitles your account to launch instances from the vendor’s image. The
software runs inside your own VPC, on infrastructure you control and pay for, which means
you are responsible for the instance, its networking, its patching cadence where the
vendor does not handle it, and its backups. Vendors typically publish recommended instance
types; treat those as a starting point and validate against your own load rather than
accepting them uncritically, since recommendations tend toward the generous.
Container products
Images are pulled into ECS or EKS the same way any other image would be. Licensing is
enforced through the subscription rather than through keys embedded in the image, so
scaling replicas is usually straightforward — though products billed per node or per
task will scale in cost alongside.
SaaS listings
Nothing is deployed into your account. You subscribe, the vendor provisions on their
side, and integration happens over the network. The operational burden is lowest here, and
in exchange your data leaves your AWS environment — which is a security review
question rather than a technical one, and worth raising before subscribing rather than
after.
Metering and how usage is counted
Usage-based products report consumption back to AWS through a metering API. When
reconciling a bill, remember that the vendor’s definition of a unit governs what you are
charged for, and definitions vary: an “endpoint” or a “node” may mean something narrower
or broader than you assume. If the metric is central to your cost, confirm the definition
in the listing before committing to an annual term.
Common mistakes when buying through Marketplace
- Evaluating the licence price in isolation. The EC2 instances underneath frequently cost more than the software, particularly for products that recommend large instance types.
- Leaving subscriptions running after evaluation. Hourly products keep billing while instances run; an abandoned proof of concept is a recurring charge nobody is watching.
- Letting anyone subscribe. Without an IAM or service control policy restricting it, any principal with sufficient permissions can commit real money on the organisation’s behalf.
- Committing annually before load-testing. An annual term locks in a pricing dimension that may scale badly once real usage arrives.
- Assuming AWS supports the product. AWS supports the platform and the billing; the seller supports the software, on whatever terms their listing sets.
- Overlooking the AWS-native equivalent. Several Marketplace categories overlap with services AWS already provides, sometimes at lower total cost.
Categories worth knowing in the catalogue
AWS Marketplace lists thousands of products, which makes it hard to navigate without a
sense of where the useful density is. A few categories account for most real purchasing.
Network and perimeter security
Next-generation firewalls, web application firewalls and secure gateways from
established network vendors, deployed as appliances inside your VPC. Organisations
frequently buy here because they already run the same vendor on-premises and want
consistent policy across both environments — that continuity is worth more than any
individual feature.
Observability and logging
Monitoring, log aggregation and application performance monitoring products. This is
one of the categories that overlaps most heavily with AWS-native services, so the honest
question is whether the third-party product’s capability or your team’s existing
familiarity justifies the additional cost over CloudWatch.
Data integration and analytics
ETL tooling, data catalogues, business intelligence platforms and commercial database
engines. Useful where an organisation has standardised on a particular analytics stack and
wants it running close to the data rather than pulling data out to it.
Developer productivity
Build tooling, artefact repositories, code quality and testing products. Frequently
purchased as SaaS listings rather than deployed, since the operational overhead of running
them yourself rarely pays for itself.
Machine learning models and data sets
Pre-trained models deployable through SageMaker, and licensed data sets through AWS Data
Exchange. The value here is time: buying a model that is good enough is often faster than
assembling training data and building an equivalent, particularly for well-established
tasks like document extraction or speech transcription.
A sensible evaluation process
Because Marketplace makes it so easy to subscribe, it is worth having a light process
rather than none. A workable sequence:
- Check for an AWS-native equivalent first and establish why it is insufficient, if it is.
- Read the pricing dimension and model it against your projected usage twelve months out, not today’s.
- Add the underlying infrastructure cost for AMI and container products, using the vendor’s recommended instance types as an upper bound.
- Deploy into an isolated test account and run it against realistic load rather than a demonstration data set.
- Review the licence terms and support commitments attached to that specific listing.
- Request a Private Offer before committing at any meaningful scale, since listed prices are a starting point.
- Decide who may subscribe and enforce it through IAM or service control policies before rolling out more widely.
None of this takes long, and it prevents the two most common outcomes: paying for
something AWS already provides, and discovering a pricing dimension that scales badly only
after signing an annual term.
Important considerations
The configurations describe account state only. They do not confer
entitlement to any specific software, any seller privileges, or any commercial terms with
any vendor. Anything your project depends on should be confirmed before ordering.
Software costs are separate. Marketplace is a procurement channel.
Subscribing to a product incurs that product’s own charges, on top of the AWS
infrastructure it runs on.
Verification processes belong to AWS. Any account verification,
review or approval is performed by AWS according to its own requirements. Nothing on this
page describes a way to alter, shortcut or influence those processes, and none is
implied.
Provider terms apply. See the
AWS Marketplace terms
and the AWS Customer Agreement.
Prices are per configuration, exactly as listed.
Frequently asked questions
Which configuration should I choose?
Match the configuration to the workload rather than to the price. Most people who buy AWS Marketplace account configurations start from the smallest option that covers their current need and move up once real usage is measured, which avoids paying for headroom that never gets used. The comparison sections above set out the trade-offs; the FAQ page covers ordering questions.
Is it safe to buy AWS Marketplace account configurations listed here?
Every configuration on this page states its specification and price exactly as supplied, and nothing is implied beyond what is written. Anything your project depends on that is not named should be confirmed on the contact page before you buy AWS Marketplace account configurations.
What is AWS Marketplace used for?
Finding, buying and deploying third-party software that runs on AWS, with charges
consolidated onto the AWS bill rather than handled through separate vendor contracts.
Is Marketplace software more expensive?
Not inherently. Listed prices are set by sellers and are frequently comparable to
buying direct. The saving is usually in procurement time rather than in unit price, and
Private Offers exist for negotiated terms at scale.
Do I still need an AWS account to run the software?
For AMI and container products, yes — they run on your own AWS infrastructure,
which is billed separately. See Buy AWS Account.
SaaS listings run on the vendor’s infrastructure instead.
Can I cancel a subscription?
Cancellation terms depend on the pricing model. Hourly products stop charging when you
stop running them; annual subscriptions run their term. Check the individual listing.
Who provides support for Marketplace software?
The seller, according to the terms of their listing. AWS supports the Marketplace
platform and billing, not the third-party product itself.
How do I control Marketplace spending?
Restrict who may subscribe using IAM policies or service control policies, tag
Marketplace resources, and review Marketplace charges separately in Cost Explorer.
How do I order?
Select the configuration above, add it to the cart and complete checkout through the
configured cryptocurrency gateway.
Where to buy AWS Marketplace account configurations
Everything needed to buy AWS Marketplace account configurations is on this page — the full list of 2 options, the price of each, and the specification each one carries.
Every configuration described above can be ordered directly from this page. Select the one you need in the selector at the top, add it to the cart and complete checkout — there are 2 configurations listed, $90.00 – $750.00. Checkout collects only a name and an email address, and payment runs through the cryptocurrency gateway configured on this site.
If you are unsure which option fits, describe the workload on the contact page before ordering rather than after — it is usually possible to narrow the list quickly. Common questions are collected on the FAQ page.
What you get when you buy AWS Marketplace account
Every listing on this page is a specific, named configuration rather than an open-ended arrangement. When you buy AWS Marketplace account here you are choosing one of the 2 configurations described above, at the stated price $90.00 – $750.00, with the specification exactly as written.
- The exact configuration named in the selector, with no substitutions.
- The price shown, with no added fees at checkout.
- A checkout that asks only for a name and an email address.
- Direct contact before ordering if you are unsure which option fits.
If you are comparing providers rather than configurations, the Cloud Accounts and Cloud Infrastructure categories list the alternatives side by side. If you already know what you need, you can buy AWS Marketplace account configurations directly from the selector at the top of this page.
Related products
See Buy AWS Account for the AWS compute these
products run on, and Buy Amazon SES Account
for AWS email infrastructure. Other platforms are listed under
Cloud Accounts. Questions are answered on
the FAQ page or via the contact page.
Reviews
There are no reviews yet.