KnowledgeGraph Visualizer - Production Readiness and User Guide

Executive Summary

Amazon Neptune stores the enterprise knowledge graph, but users need a business-friendly and application-specific way to browse the ontology, inspect relationships, search resources, validate graph structure, and share findings. The KnowledgeGraph Visualizer was built to fill that gap.

The tool provides a visual graph exploration layer over Neptune data. Users can search by label, URI, or resource type, select a node, view its connected neighborhood, inspect properties and relationships, run approved governance checks, and validate that Neptune data is usable for business and technical workflows.

Why This Tool Was Built

User Journey

High-level journey from opening the application through search, graph inspection, governance checks, and sharing findings.

Audience Guide

How To Use The Tool To Browse Neptune Data

1. Open the Choreo-hosted web application URL for the correct environment.
2. Confirm the Neptune badge shows connected. If it shows disconnected, use /api/neptune-status or the support section below.
3. Use the Neptune search box to search by business label, URI fragment, ontology class, policy term, or resource type.
4. Select a search result to render the graph neighborhood for that resource.
5. Use the graph controls to fit, zoom, switch layout, export PNG, or expand related nodes.
6. Click nodes to inspect labels, types, data properties, object relationships, and incoming links.
7. Use governance and validation views to review warnings, data quality concerns, and ontology structure.
8. Share findings with screenshots, graph exports, resource URIs, or validation notes.

Expected User Outcomes

Architecture Diagrams

The application uses a web app and backend service boundary. The browser calls Choreo, Choreo routes to the Python service, and only the Python service communicates with Neptune.

Development Architecture

Development uses the non-production Choreo web app and API gateway, a Python service component, Choreo configs/secrets, cached TTL files, optional S3 bulk load, and the development Neptune endpoint.

Production Architecture

Production should use authenticated browser access, production Choreo gateway controls, backend authorization, IAM role or workload identity for AWS access, strict CORS, and read-only defaults.

Development And Production Environment Model

Required Production Information To Finalize

Production Readiness Requirements

Go-Live Checklist

Recommended Production Feature Flags

APP_ENV=production
NEPTUNE_READ_ONLY=true
ENABLE_NEPTUNE_WRITES=false
ENABLE_DESTRUCTIVE_ENDPOINTS=false
ENABLE_SPARQL_WORKBENCH=false

Security Model

Security Principles

Endpoint Classification

Testing And UAT Plan

Smoke Tests

Regression Test Areas

• Navigation between Ontology Explorer, Governance, Neptune, and Compare views.
• Search index build or fetch behavior.
• Graph rendering after search, expand, fit, zoom, and layout changes.
• Resource details for nodes with data properties and object relationships.
• Error behavior when Neptune is unreachable or AWS identity is invalid.
• CORS behavior from the approved web app origin only.

Operations And Support

Operational Checks

Common Issues

Reference Links

• Choreo configurations and secrets
• Choreo web app managed authentication
• Amazon Neptune IAM authentication
• Amazon Neptune data access IAM policies
• Amazon Neptune IAM data access actions

Support Contact

In case of any issue with this application, Neptune graph browsing, Choreo deployment, or production readiness questions, please contact guptara@chubb.com.