Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
AWS Glue
Defines source-aware Data Catalog, crawler, classifier, connection, ETL job, trigger, schema, lineage, security, and run review, evidence handling, and action boundaries.
Read the fileOverview
AWS Glue Overview
Source-aware tool bundle for Data Catalog, crawler, classifier, connection, ETL job, trigger, schema, lineage, security, and run review, evidence reconciliation, reviewable decisions, and controlled.
Read the fileWorkflow
AWS Glue Source-Aware Triage
Inspect-first workflow for Data Catalog, crawler, classifier, connection, ETL job, trigger, schema, lineage, security, and run review.
Read the fileTemplate
AWS Glue review brief
Review-ready artifact for Data Catalog, crawler, classifier, connection, ETL job, trigger, schema, lineage, security, and run review, evidence quality, verification, and controlled actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in AWS Glue
- Teams working in Technology, Business operations
When to use it
- A proposed AWS Glue configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare an aws glue review brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- AWS Glue review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review AWS Glue and produce AWS Glue review brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with AWS Documentation — Dg / What Is Glue, then confirm that the reference is current and applicable. Inspect AWS Glue before drafting.
Context path: bundles/tools/aws-glue
What the bundle includes
Tools
- AWS Glue
Frameworks
- source-evidence matrix
- AWS Glue application matrix
- qualified-review gate
Evaluations
- AWS Glue source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use the listed authoritative or identified source surfaces for general AWS Glue guidance; local facts, configuration, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for AWS account and region, Glue version, IAM role and Lake Formation policy, data locations, catalog database and tables, crawler classifiers and change policy, job code and arguments, connections, triggers, encryption, logs, costs, tests, and rollback.
- Do not infer schema, partition, permission, job result, data quality, lineage, cost, or production readiness.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that create or alter catalog objects, crawlers, jobs, triggers, connections, IAM or Lake Formation permissions; run workloads; read or write data; delete resources; or incur spend.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.