CoreModelsGuides
AWS Glue
Stop treating a crawler snapshot as the meaning of your lake.
- Ten Minutes to a Governed Glue CatalogQuickstart · Open a terminal. Everything in this tutorial is one AWS CLI command and two HTTP calls, and at the end of it your AWS Glue Data Catalog has a governed twin in CoreModels plus a first drift audit you can read line by line. Nothing gets installed in your AWS account, no IAM role is granted to us, and no credential of yours travels anywhere: you run the CLI, you upload the JSON it printed.
- The AWS Glue Integration API, Route by RouteAPI · CoreModels models vendor governance as a small, fixed set of verbs and applies them uniformly to every connector. For AWS Glue Data Catalog — vendor key glue — that is eight core routes on the interactive surface and two on the machine-to-machine surface. (A newer sync-plan surface — sync/propose, plan fetch, and the sync ledger — sits beside these and is not covered here.) This is the reference: the exact paths, the role each one enforces, the request bodies as the API defines them, and the responses you actually get back.
- Handing the Glue Catalog to an Agent: CoreModels over MCPMCP · An agent that can answer *"did our lake drift?"* needs three things: a way to reach the governed model, a way to hand it a fresh catalog export, and a guarantee that asking the question cannot change the answer. The CoreModels MCP server provides all three. The same vendor-integration engine behind the HTTP routes is exposed as MCP tools, with the read verbs at Viewer role and the write verbs behind an admin endpoint and real project membership.
- Automating Glue Drift: The Gate, the Trail, and the HeartbeatAutomation · Nothing in your repository changes when a crawler retypes a column. That is the awkward fact about lake governance: the estate you need to watch does not live in git, so the usual "run it on pull requests" reflex leaves the interesting drift entirely unobserved. A Glue drift gate has to be driven by a clock, not by a commit — and once it is, three more mechanisms fall out of it almost for free: a rolling trail, a status badge, and a server-side heartbeat that watches the *other* direction of drift.
- What Happens to a Glue Table on Its Way into the GraphDeep dive · Take one entry out of an aws glue get-tables response — a table called events in database lake, a few columns, one partition key, a classification parameter, an S3 location — and follow it into CoreModels. By the end it is a governed Type with Elements, a vendor identity, a metadata mixin, an entry in an estate snapshot, and a set of audit rules watching it. This is that journey, plus the honest edges: what is approximated, what is deliberately not invented, and which behaviors will surprise you.
Start building
14-day free trial. Builder $49/mo after the trial. Cancel any time.