← All posts

☁️AWS from Zero

GLUE 7 · Part 808 of 1125
2 min read

AWS Glue: Get blueprint run from the CLI

#aws#cli#glue#analytics#etl
📑 On this page

Part 808 of AWS from Zero. This is lesson 7 in the AWS Glue track.

What we are learning

Use get-blueprint-run to read or inventory blueprint run in AWS Glue. This lesson identifies the required input shape, saves the raw response, and keeps inspection separate from execution.

The AWS CLI operation is aws glue get-blueprint-run. Required operation inputs: --blueprint-name (string), --run-id (string). The modeled top-level response contains BlueprintRun.

Before you run it

aws sts get-caller-identity
REGION="${AWS_REGION:-ap-south-1}"
BLUEPRINT_NAME="replace-with-blueprint-name"
RUN_ID="replace-with-run-id"
aws glue get-blueprint-run help

Use a sandbox account or an approved learning environment. Read the operation help before supplying identifiers, ARNs, network ranges, policy documents, or customer data.

Cost note: Crawlers, jobs, DataBrew, interactive sessions, and catalog usage can incur charges.

The command

aws glue get-blueprint-run \
  --blueprint-name "$BLUEPRINT_NAME" \
  --run-id "$RUN_ID" \
  --region "$REGION" \
  --output json > part-808-response.json

The response is saved to part-808-response.json so inspection is separate from execution. The explicit variables above keep required identifiers visible before the API call.

Inspect the result

node -e "const r=require('./part-808-response.json'); console.log(Object.keys(r))"
node -e "const r=require('./part-808-response.json'); console.log(JSON.stringify(r, null, 2))"

Compare the returned identifiers and status fields with the account, Region, and resource you intended to target. For asynchronous operations, continue with the service's matching get, list, or describe command until it reaches a terminal state.

One tiny variation

node -e "const r=require('./part-808-response.json'); console.log(JSON.stringify(r["BlueprintRun"], null, 2))"

This variation changes output inspection rather than adding another infrastructure concept. Keep the raw JSON while developing a query so a narrow projection does not hide an error or unexpected field.

Common mistake

An empty response does not always mean the resource is absent. Confirm the account, Region, pagination behavior, filters, and caller permissions before concluding that nothing exists.

Cleanup

# This operation is read-only, operational, or needs resource-specific rollback.
# Re-read the command output before changing shared infrastructure.
rm -f part-808-request.json part-808-response.json part-808-payload.bin part-808-debug.log

Local request and response files may contain account IDs, ARNs, names, or service configuration. Remove them when the lab is complete and follow dependency-aware cleanup for any AWS resource you created.

Next, we will learn AWS Glue: Create blueprint from the CLI.

Official AWS CLI reference