OpenLink Software · Virtuoso SaaS · Buyer Guide

From a Marketplace click to your first SPARQL query — one ordered hour, zero support tickets.

The buyer's runbook for one Virtuoso SaaS Single Server on AWS.

If you can follow eight ordered steps, you can operate a production Virtuoso — purchased, provisioned, secured, and correctly billed.

12 · 24 · 36Contract terms, in months
1112TLS SQL port — closed by default
8Phases from click to healthy
7Point onboarding checklist
The Proposition

One guide, one instance, one clean path.#

Everything the buyer portal shows you — and everything it does not — in a single, ordered runbook.

This guide covers purchasing, setting up, and operating one Virtuoso SaaS Single Server through AWS Marketplace and the buyer portal — from contract selection to your first SQL and SPARQL connections, then through daily operations, billing, and troubleshooting.

It begins where every buyer must begin: the AWS Marketplace product page — never a bookmarked fulfillment URL, because the Marketplace supplies a one-time setup context only after a successful purchase.

Prices and offer terms shown in the guide are illustrative only. The live Marketplace offer is authoritative, and AWS Marketplace remains the billing authority that issues the invoice.

After the agreement is created, you bind one buyer portal account per buyer AWS account, wait for the instance to become running and healthy, and connect over Conductor, HTTPS SPARQL, and TLS SQL on port 1112.

Which buyer are you?

Three doors into the same offer.#

Every buyer arrives with a different history. This connector matches your situation to the right entry into the AWS Marketplace offer — so you skip the preamble and start where you already are.

01 · Existing customer

Managed edition, plus the services you already trust.

You are an existing customer that seeks a managed server edition of Virtuoso, combined with the experienced services capabilities we provide.

Your entry: start with the managed edition, backed by OpenLink professional services.
02 · Evaluator → PoC

Evaluation done. Now make it real.

You have successfully evaluated the commercial edition using the free evaluation offers — and you are ready to commence a proof of concept, or you are already at the point of rollout.

Your entry: carry the evaluation into a PoC or direct rollout on the Marketplace offer.
03 · Builder → rollout

Built it. Now roll it out to customers.

You have successfully built a modern agentic solution — or revamped a struggling app or service — that now requires rollout to your customer base via the resilience offered by a cloud platform.

Your entry: roll out on Amazon Web Services through the Marketplace offer.
The Buyer Journey

Eight ordered phases, one workflow.#

Skip a phase and the portal will tell you. Follow them in order and provisioning is a formality.

1

Before You Purchase

Sign in to the AWS account that will own and pay for the agreement. Review the live Marketplace offer — term, plan, taxes, metered overages, EULA, support, and renewal terms. Use an email address that will remain available, and keep the Marketplace tab open until the confirmation page offers Set up your account.

Virtuoso SaaS Single Server — updated AWS Marketplace listing logo
01 · Marketplace product — updated listing logo
2

Purchase a Marketplace Contract

Open Virtuoso SaaS Single Server and choose View purchase options. Select the duration — 12, 24, or 36 months — then exactly one plan dimension for the required tier. Review usage-based charges, accept the terms and EULA, choose auto-renewal, and select Subscribe. Confirm tier, duration, price, tax, and renewal before subscribing.

Selecting contract duration — 12, 24, or 36 months
02 · Contract duration
3

Set Up Your Buyer Portal Account

After confirmation, select Set up your account. AWS Marketplace opens the Virtuoso SaaS identity flow and binds the buyer context to the portal account. Sign in with an existing account, or Create an account and complete signup. Use one portal account per buyer AWS account.

Signing in to the Virtuoso SaaS buyer portal
08 · Portal login
Creating a new buyer portal account
09 · Portal signup
4

Wait for Provisioning

The portal creates one tenant instance per active subscription. Open Instances and wait for status running and health healthy. Provisioning takes several minutes — refresh the Instances page rather than repeating Marketplace setup.

Instance list showing status running and health healthy
13 · Instance list
5

Connect to Virtuoso

The instance detail page provides the endpoint values and database credentials. Open Conductor for browser administration and the HTTPS SPARQL link for the query editor, signing in with the dba username and the shown password. A simple first query:

SELECT * WHERE { ?s ?p ?o } LIMIT 10
Instance detail page with endpoints and a masked database password
11 · Instance details & credentials
6

Allow TLS SQL Access

TLS SQL is closed by default. Enter only the trusted public IPv4 CIDR ranges permitted to connect to port 1112, then select Update Secure SQL Access. A single address uses /32 (e.g. 203.0.113.45/32); separate ranges with commas; leave the field empty to remove public access. 0.0.0.0/0 is not permitted.

Configuring allowed IPv4 CIDR ranges for TLS SQL
10 · Secure SQL CIDR
7

Run Daily Operations

Use lifecycle controls to Stop, Start, and Delete the instance. Connect over TLS SQL with isql <hostname>:1112 -E dba and confirm with a status(); call. Access the container shell via the buyer-specific IAM policy, role ARN, external ID, and generated AWS CLI script, and follow the online backup and recovery runbook.

Container shell access with IAM policy and role ARN
15 · Container shell access
8

Manage Billing, Renewal & Cancellation

Review usage and billing in the portal, but remember AWS Marketplace is the billing authority and issues the invoice. Review your profile and agreement in Settings, manage auto-renewal in the Marketplace subscriptions console, and follow the agreement terms for cancellation, refund, or early termination.

Usage and Billing page showing plan and estimated overage
19 · Usage & billing
The Proof

Seven proofs you are onboarded.#

✓

Marketplace subscription completed for the intended buyer AWS account.

✓

Buyer portal account created or signed in.

✓

Instance status is running and health is healthy.

✓

Conductor and SPARQL endpoint links respond.

✓

TLS SQL works from an explicitly allowed CIDR and is rejected outside it.

✓

Database credentials have been stored securely.

✓

Renewal preference has been reviewed in AWS Marketplace.

Second Runbook · Backup & Restore

Back up in the portal. Restore only through OpenLink.#

A companion runbook to the buyer guide: run your own online backups, and let OpenLink run the controlled restores.

⚖️

Scope. Buyers can run an online backup, confirm the backup-sync, and retain the backup date, time, and durable S3 prefix. Buyers cannot run a restore directly — a restore replaces the active database, requires a service outage, and is performed only by OpenLink seller administrators after explicit buyer authorization.

1

Before You Start

You need buyer portal access, a running Virtuoso instance, buyer AWS IAM credentials with the one-time shell-access policy, and AWS CLI v2 with the Session Manager plugin. Use the tenant-specific script from the portal — never reuse a script from another buyer, instance, or environment.

2

Run an Online Backup

Sign in to the portal, open Instances and select the running instance, open Backup & Recovery, and copy or download the Run online backup script. Run it in a terminal configured with the buyer IAM user or role, and wait. The script assumes the scoped ECS Exec role, configures the backup directory, runs backup_online('virtuoso_#', …), starts a Fargate sync task to durable S3, and reports success only on exit code 0.

3

Verify the Backup

A successful script reports the durable S3 backup prefix. Record the instance ID and project name, the completion date and UTC time, the backup prefix or backup-set timestamp, and the script output confirming the S3 sync. The S3 bucket is managed by OpenLink — do not alter, delete, or replace objects in the managed prefix.

4

Request a Restore

A restore is not online: it replaces the active database and can discard later changes. Submit a support request with the buyer AWS account ID and portal email, instance ID and project name, the backup date/time or prefix, explicit authorization, outage confirmation, and a technical contact. OpenLink verifies ownership, creates a rollback copy, stops the tenant, restores the set, restarts Virtuoso, and confirms. Do not delete the instance to request a restore.

5

Validate After a Restore

After OpenLink confirms, open the instance in the portal, confirm status running and health healthy, verify the expected database content in HTTPS Conductor, run an application-level or SQL validation, and run a new online backup if the restored state must be protected immediately.

Backup Troubleshooting

Four backup situations, resolved.#

The Backup & Recovery section is missing▼

The instance may still be provisioning, stopped, or missing required backup metadata. Confirm it is running and healthy; if the section does not appear, contact OpenLink support with the instance ID.

The backup script reports no running ECS task▼

Start the instance from its detail page, wait until its health is healthy, then rerun a newly copied script from the buyer portal.

The script reports an AWS access error▼

Use a buyer IAM user or role, not AWS root credentials. Confirm the one-time buyer shell-access policy is attached and use the latest script from the instance detail page.

I need a different recovery point▼

Do not run an older script or modify the generated restore guidance. Request a seller-admin restore and identify the desired backup date/time in the support request.

Questions & Troubleshooting

Twelve questions a buyer meets most often.#

The portal has no instance — what should I check?▼

Confirm the AWS Marketplace agreement is active in the same buyer AWS account used for setup. Open Set up your account from the active agreement, not an old bookmarked URL, sign in with the portal account bound to that buyer account, then refresh Instances and wait for provisioning to complete.

Why do I see "wrong user for this Marketplace setup link"?▼

Sign out of the buyer portal, reopen Set up your account from the active Marketplace agreement, and sign in with the portal account previously bound to that buyer AWS account.

A setup link has expired or is invalid — can I reuse it?▼

Do not reuse it. Open the active agreement in AWS Marketplace and choose Set up your account again to receive a fresh one-time setup context.

TLS SQL cannot connect. What should I verify?▼

Confirm the source public IP is included in Allowed IPv4 CIDRs and that the client uses TLS on port 1112. A self-signed certificate warning is expected unless the client trusts the tenant certificate.

Can I bookmark or open a fulfillment URL directly?▼

No. Start from the AWS Marketplace product page. The Marketplace supplies a one-time setup context only after a successful purchase, so a saved fulfillment URL will not work on a later visit.

How many buyer portal accounts should I use per AWS account?▼

Exactly one portal account per buyer AWS account. Reuse that account for future portal access and for any additional Marketplace setup links associated with the same buyer account.

Can I open Secure SQL to 0.0.0.0/0?▼

No — 0.0.0.0/0 is not permitted. Allow only the trusted public IPv4 CIDR ranges that need port 1112, and leave the field empty to remove public TLS SQL access entirely.

Does turning off auto-renewal end my current term?▼

No. Turning off auto-renewal applies to the next renewal only. It does not terminate an active contract and does not automatically remove a tenant.

What does Delete Instance do?▼

Delete Instance terminates the tenant infrastructure. It is not a substitute for cancelling or changing a Marketplace agreement.

How long does provisioning take?▼

Several minutes. Refresh the Instances page rather than repeating Marketplace setup while an instance is already provisioning, and wait for status running and health healthy.

Where is billing authoritative?▼

AWS Marketplace remains the billing authority and issues the invoice. The buyer portal's Usage & Billing page shows operational estimates for plan, instance hours, contract amount, and storage or data-transfer overage.

Should I expect a self-signed certificate warning on TLS SQL?▼

Yes. A self-signed certificate warning is expected unless the client trusts the tenant certificate. It does not indicate a failed connection.

Core Technical Glossary

Twelve terms, defined once.#

Virtuoso SaaS Single Server

The managed, single-server Virtuoso offering purchased through AWS Marketplace — one tenant instance per active subscription.

AWS Marketplace

The commerce platform where the contract is purchased, the agreement is managed, and the invoice is issued.

Buyer Portal

The web application that provisions and manages the tenant — Instances, Usage & Billing, Settings, and Secure SQL access controls.

Conductor

Virtuoso's browser-based administration interface, reached over HTTPS from the instance detail page.

SPARQL Endpoint

The instance's HTTPS SPARQL query endpoint, opened from the instance detail page with the database credentials.

Secure SQL (TLS)

TLS-encrypted SQL/ODBC/JDBC access on port 1112 — closed by default and opened only for allowed public IPv4 CIDR ranges.

isql

Virtuoso's interactive SQL command-line client, used over TLS as isql <hostname>:1112 -E dba.

CIDR

Classless Inter-Domain Routing notation for allowed IP ranges — a single address uses /32, e.g. 203.0.113.45/32.

Metered Overage

Usage-based charges applied in addition to the contract price when usage exceeds the included entitlement.

EULA

The End-User License Agreement reviewed and accepted during the Marketplace purchase.

Auto-Renewal

Automatic agreement renewal at term end; turning it off prevents the next renewal but does not end the active term.

ECS Exec

AWS ECS Exec shell access to the instance container, gated by a buyer-specific IAM policy, role ARN, external ID, and generated AWS CLI script.

Online backup

An online (hot) Virtuoso backup run from the buyer portal while the instance stays running, via backup_online().

Backup chain

The full backup established by the first successful run, followed by per-instance daily incremental backups.

Durable S3 prefix

The OpenLink-managed S3 location holding the synced backup set; buyers must not alter, delete, or replace its objects.

Seller-admin restore

A controlled restore performed only by OpenLink after explicit buyer authorization, replacing the active database and requiring a service outage.

Rollback copy

A copy of the current database files created before a restore, retained for the configured period.

Fargate sync task

The scoped AWS Fargate task the backup script starts to copy the backup set to durable S3.

Knowledge Graph ExplorerDrag, filter, and resolve the buyer guide as a graph▼
Knowledge Graph Explorer

The buyer guide, as a graph.#

Every entity — the guide, its phases, the software, the organizations, and every question and term — is a node. Drag to pin, double-click to unpin, click a node or edge to resolve it. Click the graph pane once to arm pan/zoom.

0 nodes · 0 links

Advanced settings

Physics

Predicate filters

Node filters

Legend

SPARQL WorkbenchRun and edit live queries against the uploaded graph▼
SPARQL Workbench

Test the graph, live.#

Run the recipes against the uploaded graph on URIBurner, or edit the query and run your own.

Query the buyer-guide knowledge graph

Queries are scoped to the named graph uploaded at linkeddata.uriburner.com.

Format guidance: SELECT → text/x-html+tr · DESCRIBE/CONSTRUCT → text/x-html-nice-turtle
Entity-type summary ▼
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?type (SAMPLE(?s) AS ?sampleEntity) (SAMPLE(?label) AS ?sampleLabel) (COUNT(?s) AS ?entityCount)
WHERE {
  GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/virtuoso-saas-managed-service-buyer-guide-deepseek_v4pro-1.ttl> {
    ?s rdf:type ?type .
    OPTIONAL { ?s rdfs:label ?label }
  }
}
GROUP BY ?type ORDER BY DESC(?entityCount)
Smoke-test query ▼
SELECT * WHERE { ?s ?p ?o } LIMIT 10
Count triples ▼
SELECT (COUNT(*) AS ?triples) WHERE { ?s ?p ?o }
List entities by type ▼
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?type (SAMPLE(?s) AS ?sampleEntity) (SAMPLE(?label) AS ?sampleLabel) (COUNT(?s) AS ?entityCount)
WHERE {
  GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/virtuoso-saas-managed-service-buyer-guide-deepseek_v4pro-1.ttl> {
    ?s rdf:type ?type .
    OPTIONAL { ?s rdfs:label ?label }
  }
}
GROUP BY ?type ORDER BY DESC(?entityCount)