You know Virtuoso. Now you want it managed.
You already use Virtuoso and want a managed server edition backed by OpenLink’s experienced services team.
One tenant instance for an active subscription, purchased through AWS Marketplace and administered through the buyer portal.
Single Server · AWS Marketplace purchase · Buyer portal setup
Whether you are extending an existing deployment, moving beyond evaluation, or bringing a solution to customers, the Virtuoso SaaS offer on AWS Marketplace gives you a place to begin.
You already use Virtuoso and want a managed server edition backed by OpenLink’s experienced services team.
You have successfully evaluated the commercial edition through the free evaluation offers. Now you are ready to begin a proof of concept (PoC) or move into rollout.
You have built a modern agentic solution, or revamped a struggling application or service. Now you are ready to roll it out to your customer base, with cloud-platform resilience as a deployment requirement.
Start with the Marketplace offer. Match the service tier to your next stage, and align the services and support you need with OpenLink. The buying guide below takes you from agreement to a working instance.
Explore the AWS Marketplace offer ↗Choose the service tier and contract duration that fit your requirements. The guide describes 12-, 24- and 36-month public-offer terms; check the live offer before committing. Metered overages, where applicable, sit alongside the contract price. Screenshot prices are illustrative.
Review the tier, duration, taxes, overages and renewal choice before subscribing.
See the current Marketplace offer ↗Marketplace creates the agreement and supplies the setup context. The portal binds it to the account for that buyer AWS account, then provisions one tenant instance. If the setup link expires, reopen Set up your account from the active agreement.
Use the current endpoint values on the instance detail page. HTTPS Conductor is the administration interface. HTTPS SPARQL is the query endpoint. Secure SQL, ODBC and JDBC clients use TLS on port 1112, after you allow their public IPv4 CIDRs.
Browser administration interface.
Query editor and endpoint.
TLS on port 1112. Allowed CIDRs required.
SQL access starts closed. Use trusted public IPv4 ranges; /32 permits a single address. Leave the field empty to remove public access. 0.0.0.0/0 is not permitted.
Start and stop control the tenant. Delete terminates tenant infrastructure. Renewal and cancellation concern the Marketplace agreement. Review each in its own place.
Stops the running tenant while retaining its data.
Resumes a stopped tenant. Allow several minutes for endpoint health checks to recover.
Terminates the tenant infrastructure. It does not cancel or change the Marketplace agreement.
Prevents the next renewal. It does not end the active contract or automatically remove a tenant.
Shows operational estimates, including instance hours and estimated overages. AWS Marketplace remains the billing authority and issues the invoice.
Follow the agreement terms and contact OpenLink support or AWS Marketplace Support for cancellation, refund or early termination requests.
Run backups while Virtuoso stays online. Confirm that the backup set reached durable S3 storage. If you need to recover, authorize OpenLink to restore a selected backup set during an agreed service outage.
Use your instance’s generated script from Backup & Recovery. It runs an online Virtuoso backup and waits for the S3 sync task to finish.
Buyers cannot restore directly. OpenLink seller administrators replace the active database only after explicit buyer authorization and acceptance of the expected outage.
Use a running instance, buyer IAM credentials with the one-time shell-access policy, AWS CLI v2 and the Session Manager plugin. Copy the latest tenant-specific script; do not reuse one from another buyer, instance or environment.
The generated script reports success only when the scoped Fargate sync task exits with code 0. Retain that output and the reported durable S3 prefix.
The first successful run establishes a full backup chain. The service then runs a per-instance daily workflow that creates incremental backups and copies them to the same durable S3 location.
OpenLink manages the S3 bucket. Do not alter, delete or replace objects in the backup prefix. Ask OpenLink support for independent S3 verification, supplying the instance ID and prefix.
Restoring is not an online operation. It requires a service outage and can discard changes made after the selected backup. Deleting an instance is a termination action, not a recovery request.
Buyer AWS account ID and buyer portal email address.
Instance ID and project name.
Backup date/time or backup-set prefix to restore.
Explicit authorization to replace the current database state.
Confirmation that the expected service outage is acceptable.
Technical contact to confirm post-restore validation.
Confirm that the instance is running and healthy. It may still be provisioning, stopped or missing required backup metadata. If the section remains absent, contact OpenLink support with the instance ID.
Start the instance, wait for healthy status, then rerun a newly copied script from the portal.
Use a buyer IAM user or role rather than root credentials. Check that the one-time shell-access policy is attached and use the latest instance script.
Request a seller-admin restore with the desired backup date/time. Do not run an older script or modify the generated restore guidance.
Use this checklist to record what you have verified. These checkmarks are a personal aid; they do not test or change your tenant.
Ready when you have verified each item.
Seven steps from the buyer guide.
Sign in to the AWS account that will own and pay for the agreement. Review the live offer, term, selected plan, taxes, overages, EULA, support and renewal terms. Select exactly one plan dimension, accept the terms and subscribe.
Keep the Marketplace tab open. After purchase confirmation, choose Set up your account. Use the fresh Marketplace setup context; do not reuse or bookmark a fulfillment URL.
Sign in to the existing portal account for this buyer AWS account, or create one. Use one portal account per buyer AWS account and reuse it for future setup links and portal visits.
Open Instances. Wait until status is running and health is healthy before using the displayed endpoints. Provisioning can take several minutes; refresh Instances rather than repeat setup.
Use the tenant-specific Conductor and SPARQL HTTPS links. The instance detail page supplies the dba username and database password. Keep the password out of tickets, screenshots, source control and shell history.
TLS SQL access starts closed. Allow trusted public IPv4 CIDRs for port 1112. Use /32 for one address; separate ranges with commas. Leave the field empty to remove public access. The range 0.0.0.0/0 is not permitted.
Confirm that Conductor and SPARQL respond and TLS SQL works from an allowed CIDR and is rejected outside it. Store credentials securely. Review renewal in AWS Marketplace, and use the linked runbooks for shell access and backup/recovery.
Buyer-operated backup, ending with durable S3 sync confirmation.
Sign in to the buyer portal and select the running instance. Use buyer IAM credentials with the one-time shell-access policy, AWS CLI v2 and the Session Manager plugin. Use a buyer IAM user or role, not AWS root credentials.
Open Backup & Recovery and choose Copy Script or Download Script for Run online backup. Run that generated script in a terminal configured with the buyer IAM user or role. Keep the terminal open while the backup-sync task runs.
The script assumes the scoped ECS Exec role, configures the backup directory, runs the Virtuoso backup online and starts a scoped Fargate task to sync the backup set to durable S3. Success is reported only when the sync task exits with code 0.
Record the instance ID and project name, completion date and UTC time, backup prefix or backup-set timestamp, and script output confirming successful S3 sync. The first successful run establishes a full backup chain; the service then runs daily incremental backups to the same durable S3 location.
Buyer authorization, seller-admin recovery, and workload validation.
Send OpenLink support the buyer AWS account ID and portal email, instance ID and project name, selected backup date/time or prefix, explicit authorization to replace the current database, acceptance of the expected outage, and a technical contact for post-restore validation.
OpenLink verifies the buyer, instance ownership and requested backup set; creates a rollback copy of the current database files; stops the tenant service and restores the selected backup; restarts Virtuoso and checks health; then confirms the result and retains the most recent rollback copy for the configured retention period.
After OpenLink confirms completion, check that the portal reports running and healthy. Open HTTPS Conductor and verify the expected database content. Run application-level or SQL validation for the workload. Run a new online backup if the restored state needs immediate protection.
isql <tenant-hostname>:1112 -E dba SQL> status();
Use your tenant hostname. Enter the password only when prompted. The guide notes that a self-signed certificate warning is expected unless your client trusts the tenant certificate.
Select exactly one plan dimension for the service tier you require.
The guide says Stop Instance retains tenant data. Start Instance resumes the stopped tenant.
Interactive graph visualization derived from the companion RDF. Click nodes to resolve, drag to explore. Graph data embedded from companion RDF at generation time.
Local collection; not published. The graph address below is the intended publication address. Live recipes require the Turtle file to be loaded at that address first. Your tenant’s SPARQL endpoint is supplied privately by your portal.
Query this knowledge graph on URIBurner. The editor opens on the canonical SAMPLE entity-type summary (DAV named graph). Pick a recipe, edit freely, then run live or copy.
Reproduced verbatim from the companion RDF. Execute loads the query into the workbench below and runs it live.
SELECT * WHERE { ?s ?p ?o } LIMIT 10Copy this example into your healthy tenant’s SPARQL editor. It may return no rows on an empty database.