App Runner: Associate custom domain from the CLI

Part 532 of AWS from Zero. This is lesson 11 in the App Runner track.

What we are learning

Use associate-custom-domain to change one App Runner configuration deliberately and inspect the resulting state. This lesson identifies the required input shape, saves the raw response, and keeps inspection separate from execution.

The AWS CLI operation is aws apprunner associate-custom-domain. Required operation inputs: --service-arn (string), --domain-name (string). The modeled top-level response contains DNSTarget, ServiceArn, CustomDomain, VpcDNSTargets.

Before you run it

aws sts get-caller-identity
REGION="${AWS_REGION:-ap-south-1}"
SERVICE_ARN="replace-with-service-arn"
DOMAIN_NAME="replace-with-domain-name"
aws apprunner associate-custom-domain 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: Provisioned memory, active compute, builds, and connected services can incur charges.

The command

aws apprunner associate-custom-domain \
  --service-arn "$SERVICE_ARN" \
  --domain-name "$DOMAIN_NAME" \
  --region "$REGION" \
  --output json > part-532-response.json

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

Do not treat a zero exit code as proof that the intended state is active everywhere. AWS control planes can be eventually consistent, and some operations start asynchronous work.

Cleanup

# This operation is read-only, operational, or needs resource-specific rollback.
# Re-read the command output before changing shared infrastructure.
rm -f part-532-request.json part-532-response.json part-532-payload.bin part-532-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 App Runner: Update default auto scaling configuration from the CLI.

Official AWS CLI reference