GuardDuty: Get administrator account from the CLI

Part 705 of AWS from Zero. This is lesson 4 in the GuardDuty track.

What we are learning

Use get-administrator-account to read or inventory administrator account in GuardDuty. This lesson identifies the required input shape, saves the raw response, and keeps inspection separate from execution.

The AWS CLI operation is aws guardduty get-administrator-account. Required operation inputs: --detector-id (string). The modeled top-level response contains Administrator.

Before you run it

aws sts get-caller-identity
REGION="${AWS_REGION:-ap-south-1}"
DETECTOR_ID="replace-with-detector-id"
aws guardduty get-administrator-account 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: GuardDuty analyzes events and data sources with usage-based pricing after any trial.

The command

aws guardduty get-administrator-account \
  --detector-id "$DETECTOR_ID" \
  --region "$REGION" \
  --output json > part-705-response.json

The response is saved to part-705-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-705-response.json'); console.log(Object.keys(r))"
node -e "const r=require('./part-705-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-705-response.json'); console.log(JSON.stringify(r["Administrator"], 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-705-request.json part-705-response.json part-705-payload.bin part-705-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 GuardDuty: Get coverage statistics from the CLI.

Official AWS CLI reference