AWS Glue Pipelines

Official · maintained by Marmot
marmotdata/gluepipeline

Discover workflows, tasks and run history from AWS Glue

Pipelines Assets Lineage Run History Experimental

The Glue Pipelines plugin discovers AWS Glue workflows as Pipeline assets, their steps as Task assets, and the run history of the workflows, jobs and crawlers in the account.

It shares the Glue provider with the Glue plugin, so a workflow step links to the job or crawler asset that plugin already created rather than a copy of it. This plugin creates no Job, Crawler, Database or Bucket assets, only the lineage edges and the run history that point at them.

Required Permissions

AWS Configuration

See AWS Configuration for the supported AWS configuration options.

Tests

Unit tests need nothing. The end-to-end tests run against a Glue endpoint:

docker run -d --name marmot-test-gluepipeline -p 15560:5000 motoserver/moto:latest
MARMOT_TEST_GLUEPIPELINE_ENDPOINT=http://localhost:15560 go test ./...

Keyless authentication

On Marmot Cloud or Marmot Enterprise the pipeline can present its own identity instead of access keys. Register your Marmot instance as an IAM OIDC identity provider (client id sts.amazonaws.com), create a role whose trust policy allows sts:AssumeRoleWithWebIdentity for that provider with <issuer host>:sub equal to the pipeline's subject, pipeline:<name> as reported by the pipeline API, and set credentials.role_arn and credentials.region. No key exists anywhere; Marmot mints a short-lived token for each run.