Aegis Gateway 2.0

Tutorials

New to Aegis? Start with the HTML Hello World guide: how Aegis fits an IDE development cycle and how to put governed MCP in front of an existing MCP server or Apache project.

Each tutorial runs real Apache software on one machine and puts Aegis between an agent and it. The outputs in each one are copied from a recorded run; the files they use are in adopters/tutorials/.

Tutorial Engines Front doors IDE setup and prompts Start here if you…
Spark and Iceberg from your IDE Spark 4.0.1 (Spark Connect) with Iceberg 1.10.1 tables on a REST catalog own host and Knox 3.0.0 VS Code, Kiro, Cursor, Claude Desktop, MCP Python SDK want the complete developer path: tiny dataset, IDE agent, governed change, both flavors
Spark and Spark Connect Spark 4.0.1: monitoring REST API and Spark Connect own host scripted client run Spark jobs and SQL through an agent
Iceberg REST catalog Iceberg 1.10.1 RESTCatalogServer own host scripted client govern catalog operations: namespaces, properties, drops
Kafka and Kafka Connect Kafka 3.9.1 KRaft broker and Connect worker own host scripted client govern topics and connectors
Flink Flink 1.20.1 own host scripted client govern jobs, savepoints and cancellation
Break-glass MCP servers Spark 4.0.1, Kafka 3.9.1, Iceberg 1.10.1 and Flink 1.20.1, one independent server each own host and stdio; Knox steps in each README IDE settings in each README want a signed server catalog and incident containment end to end

The engine profiles marked passed in examples/adopters/ also have a retained run through both front doors (own host and Knox), with the exact configuration, topology and results; the Spark and Iceberg tutorial’s run is kept there as spark-iceberg.

One tutorial per verified project, from your IDE, with and without Knox

These twenty-seven are built by tools/build-project-tutorials.py from each project’s retained run. All twenty-seven, plus Spark with Iceberg, have historical own-host and Knox Keep records, and every kept audit journal verifies. Each tutorial has the engine command line, both flavors step by step, VS Code, Kiro and Cursor files in adopters/tutorials/<project>/ide/, prompts mapped to tools with what Aegis answered, and the full request table of that run. python tools/build-project-tutorials.py --check fails when a tutorial no longer matches its kept run.

Security reviewers: start with the HTML security guide (threat zones, TM01 to TM10, OWASP MCP handling, S1 to S31) before walking a tutorial.

Project Tutorial
Apache ActiveMQ 6.3.2 (Jolokia) tutorials/activemq.md
Apache Airflow 2.9.3 tutorials/airflow.md
Apache BookKeeper 4.18.1 tutorials/bookkeeper.md
Apache Burr 0.42.0 (incubating) tutorials/burr.md
Apache Calcite 1.42.0 over Avatica 1.28.0 tutorials/calcite.md
Apache CouchDB 3.4.2 tutorials/couchdb.md
Apache Doris 4.1.3 tutorials/doris.md
Apache Druid 28.0.1 tutorials/druid.md
An existing MCP server (Python SDK and the filesystem server) tutorials/existing-mcp-server.md
Apache Flink 1.20.1 tutorials/flink.md
Apache Flume 1.11.0 tutorials/flume.md
Apache Hadoop HDFS 3.2.1 tutorials/hadoop.md
Apache HBase (REST) tutorials/hbase.md
Apache Hive 4.0.1 tutorials/hive.md
Apache Iceberg 1.10.1 REST catalog tutorials/iceberg.md
Apache Ignite 2.18.0 tutorials/ignite.md
Apache Kafka 3.9.1 and Kafka Connect tutorials/kafka.md
Apache NiFi 1.28.1 tutorials/nifi.md
Apache Pinot 1.2.0 tutorials/pinot.md
Apache Pulsar 4.0.13 tutorials/pulsar.md
Apache Ranger 2.9.0 tutorials/ranger.md
Apache Solr 9.10.1 tutorials/solr.md
Apache Spark 4.0.1 tutorials/spark.md
Apache Spark Connect 4.0.1 tutorials/spark-connect.md
Apache Storm 2.6.2 tutorials/storm.md
Apache Superset 4.0.2 tutorials/superset.md
Apache ZooKeeper 3.9.3 tutorials/zookeeper.md

The IDE files are checked by DocumentationAssetsTest (they parse and name the tutorial’s endpoints). The transport they use was exercised with the official MCP Python SDK in the Spark and Iceberg tutorial; the IDEs themselves were not driven by a test.

Projects without a tutorial

Atlas, AsterixDB, Cassandra, Impala, Paimon and SkyWalking have a configuration profile that passes the contract test, which proves route rendering and governance order, not that the product answers. None has a real run on record, so none has a tutorial.

Each one has a shareable configuration walkthrough in its adapter README (the tools it governs, the source choice, and how it would run against a real engine), clearly marked as contract-tested configuration with no kept run:

| Project | Configuration walkthrough | | — | — | | Apache Atlas | adapters/atlas/README.md | | Apache AsterixDB | adapters/asterixdb/README.md | | Apache Cassandra | adapters/cassandra/README.md | | Apache Impala | adapters/impala/README.md | | Apache Paimon | adapters/paimon/README.md | | Apache SkyWalking | adapters/skywalking/README.md | The status and blocker of each are in examples/adopters/README.md and evidence/ADOPTER-REAL-ENGINE-STATUS.md.