SQS: Create queue from the CLI

Part 348 of AWS from Zero. This is lesson 7 in the SQS track.

What we are learning

Use create-queue to create or register one SQS resource through the CLI. This lesson identifies the required input shape, saves the raw response, and keeps inspection separate from execution.

The AWS CLI operation is aws sqs create-queue. Required operation inputs: --queue-name (string). The modeled top-level response contains QueueUrl.

Before you run it

aws sts get-caller-identity
REGION="${AWS_REGION:-ap-south-1}"
QUEUE_NAME="replace-with-queue-name"
aws sqs create-queue 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: SQS requests, payload size, and data transfer can incur charges beyond the free tier.

The command

aws sqs create-queue \
  --queue-name "$QUEUE_NAME" \
  --region "$REGION" \
  --output json > part-348-response.json

The response is saved to part-348-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-348-response.json'); console.log(Object.keys(r))"
node -e "const r=require('./part-348-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-348-response.json'); console.log(JSON.stringify(r["QueueUrl"], 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 run a generated request unchanged. Replace every placeholder, add ownership tags where supported, estimate cost, and verify that the selected Region and account are disposable.

Cleanup

# Review the inverse operation before removing the demo resource.
aws sqs delete-queue help
rm -f part-348-request.json part-348-response.json part-348-payload.bin part-348-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 SQS: Add permission from the CLI.

Official AWS CLI reference