Elastic Container Registry: Delete registry policy from the CLI

Part 480 of AWS from Zero. This is lesson 19 in the Elastic Container Registry track.

What we are learning

Use delete-registry-policy to remove, stop, release, or detach one Elastic Container Registry resource in a dependency-aware way. This lesson identifies the required input shape, saves the raw response, and keeps inspection separate from execution.

The AWS CLI operation is aws ecr delete-registry-policy. Required operation inputs: none. The modeled top-level response contains registryId, policyText.

Before you run it

aws sts get-caller-identity
REGION="${AWS_REGION:-ap-south-1}"
aws ecr delete-registry-policy 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: Image storage, scanning, replication, and data transfer can incur charges.

The command

aws ecr delete-registry-policy \
  --generate-cli-skeleton input > part-480-request.json
 
# Edit every placeholder in part-480-request.json, then run:
aws ecr delete-registry-policy \
  --cli-input-json file://part-480-request.json \
  --region "$REGION" \
  --output json > part-480-response.json

The response is saved to part-480-response.json so inspection is separate from execution. Review part-480-request.json, replace every placeholder, and remove unsupported optional fields before the real call.

Inspect the result

node -e "const r=require('./part-480-response.json'); console.log(Object.keys(r))"
node -e "const r=require('./part-480-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-480-response.json'); console.log(JSON.stringify(r["registryId"], 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

Deletion and stop operations can be irreversible or blocked by dependencies. Capture the resource identifier and current configuration before running the final command.

Cleanup

# This operation is read-only, operational, or needs resource-specific rollback.
# Re-read the command output before changing shared infrastructure.
rm -f part-480-request.json part-480-response.json part-480-payload.bin part-480-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 Elastic Container Registry: Batch check layer availability from the CLI.

Official AWS CLI reference