Glossary

AWS Marketplace

Amazon’s catalogue of third-party software, bought and deployed through the AWS account you already have. A procurement shortcut for buyers and a distribution channel for vendors.

General definition

AWS Marketplace is the curated catalogue where AWS customers find, subscribe to and launch software from independent vendors. The vendor publishes the listing, but the purchase runs through the buyer’s AWS account: the charge appears on the monthly AWS invoice, a standard contract or the vendor’s EULA governs the licence, and the software lands directly in the buyer’s own account, so the data never leaves it.

Listings come in a few delivery types, and the type decides what you get after you click Subscribe:

  • AMI (Amazon Machine Image): a pre-built virtual machine image you launch as an EC2 instance, often paired with a CloudFormation template for a one-step, unattended deployment
  • Container: images and Helm charts pulled from Amazon ECR and deployed to Amazon EKS, ECS or any Kubernetes cluster
  • SaaS: the vendor hosts the service, the buyer subscribes and is redirected to register, and usage is metered back to the AWS bill
  • Professional services and data products: consulting packages and AWS Data Exchange datasets

Pricing models include free, bring your own licence (BYOL), hourly or annual per instance, usage metering and multi-year contracts. Two features matter for enterprise buyers. Private offers let a vendor send one customer negotiated terms, a custom price and custom legal documents inside the Marketplace, so procurement still happens on the AWS invoice. And Marketplace purchases can count towards an AWS Enterprise Discount Program (EDP) or private pricing commitment, so budget already committed to AWS burns down on third-party software instead of opening a new vendor relationship. Many large organisations prefer this route because it skips a separate vendor onboarding and billing review.

For a self-hosted chat or AI server, the AMI or container listing is the interesting one: the software runs inside your own VPC, under your IAM policies, with your backups and your logs. The same images usually exist on other cloud marketplaces, so the choice is about where your account and committed spend live rather than about the product.

In the Ethora ecosystem

Ethora Core is listed on AWS Marketplace as an AMI with a first-boot setup page, plus a CloudFormation template for unattended installs. The image is Ubuntu 24.04 with Docker, the public installer and every container image pre-pulled, so an install completes in about five minutes: launch the instance, point four DNS records at it, then either answer two questions on the setup page or pass the root domain and admin e-mail as stack parameters and let the stack finish on its own. Nothing is pre-configured in the image and no vendor credentials are on it; Let’s Encrypt certificates are obtained on first boot.

The result is the same stack you get from Docker Compose or the Helm chart, running in your own account and region, which is what data residency and HIPAA reviews usually ask for. Teams that would rather not run it themselves can have Ethora TechOps operate a dedicated server inside their AWS account under an enterprise SLA. The current list of channels and their status is on the Get Ethora page.

Get started

Chat and AI on infrastructure you control

Run Ethora self-hosted or dedicated, with full control of data, keys and residency. Talk to our team.

Start Free
Free tier available Enterprise SLA No vendor lock-in