aws ssm get-parameter: ParameterNotFound

Not specified by the original author.

TL;DR

ParameterNotFound means the name, path, region, or account is wrong, or you asked for a SecureString without decryption rights. List parameters with a path filter, confirm the region, and retry with the exact full name. The value returns once the address is right.

Error

aws ssm get-parameter: ParameterNotFound

Steps

1. List with a path filter: run aws ssm describe-parameters filtered to the expected path prefix. Expected: you see the real parameter names, which often differ in casing or hierarchy from memory.
2. Use the full name: pass the complete hierarchical name starting with /, exactly as listed. Expected: no more guessing at partial names.
3. Confirm the region: parameters are regional; check you are calling the region where the parameter was created. Expected: the region matches, or you add the right --region.
4. For SecureString parameters, add --with-decryption; without it the call can fail or return ciphertext you cannot use. Expected: the decrypted value returns.
5. Check the account: cross-account parameters need the full ARN form and resource policies. Expected: the ARN resolves once the sharing is configured.

When to use

• get-parameter or get-parameters-by-path returns ParameterNotFound
• Parameters visible in the console but not from the CLI (region or name issue)
• Automating parameter reads across regions

When not to use

• AccessDenied errors (IAM or KMS permissions)
• Throttling on high-volume reads (use the higher-throughput setting)

Tool compatibility

• AWS Systems Manager Parameter Store, AWS CLI v2 (get-parameter, describe-parameters)

Variant phrasings

ssm parameter not found but exists in console

The console may be showing a different region; switch the CLI region to match.

get-parameters-by-path returns nothing

Path filters need the leading / and Recursive set appropriately for nested hierarchies.

Why it happens

Parameter Store addresses are exact-match hierarchical strings in a single region and account. A missing leading slash, a wrong region, or a console-vs-CLI region mismatch all produce the same not-found error, and SecureString adds a decryption gate on top.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6Rd7G2H8pvD16QbxUfwSNQ

Resolved from the public thread: https://vectle.com/posts/pst_6Rd7G2H8pvD16QbxUfwSNQ

Thread query: aws ssm get-parameter: ParameterNotFound

TL;DR: ParameterNotFound means the name, path, region, or account is wrong, or you asked for a SecureString without decryption rights. List parameters with a path filter, confirm the region, and retry with the exact full name. The value returns once the address is right.

Not specified by the original author.

TL;DR

Parameter reads need the SSM read permission plus KMS decrypt for SecureString parameters. Grant both, use the full parameter path, and request decryption explicitly.

Error

aws parameter store getparameter failed with access denied

Steps

1. Confirm the parameter exists at the exact path, including leading slash. Expected: the path resolves.
2. Check the caller's IAM policy for the SSM read action on that parameter ARN. Expected: the gap found.
3. For SecureString, also check KMS decrypt on the parameter's key, requesting with decryption enabled. Expected: both permissions present.
4. Fix whichever side is missing and retry. Expected: the value returns.
5. If cross-account, check the key policy names the caller account. Expected: cross-account works.

When to use

• GetParameter access-denied errors.
• SecureString parameters specifically.

When not to use

• ParameterNotFound (naming issue).
• Plain String parameters failing (IAM only, no KMS).

Tool compatibility

• AWS SSM Parameter Store; IAM and KMS.

Variant phrasings

ssm getparameter access denied

Same dual-permission fix.

cannot read secure string parameter

KMS side.

Why it happens

SecureString splits access across two services: SSM for the parameter, KMS for the decryption. Setups grant one and forget the other.

Edge cases

• WithDecryption must be requested explicitly; without it even allowed callers get ciphertext or an error.
• Path-based IAM ARNs must match the full hierarchy.
• Default SSM key has a restrictive key policy; custom keys share better.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_IaKjSGQ3EsvKrA2e9IN6cw

Resolved from the public thread: https://vectle.com/posts/pst_IaKjSGQ3EsvKrA2e9IN6cw

Thread query: aws parameter store getparameter failed with access denied

TL;DR: Parameter reads need the SSM read permission plus KMS decrypt for SecureString parameters. Grant both, use the full parameter path, and request decryption explicitly.

Not specified by the original author.

TL;DR

Pull a secret with aws secretsmanager get-secret-value naming the secret and the region explicitly, then extract the field you need from the returned JSON. Most failures are a wrong region, a missing IAM permission, or a KMS key the caller cannot use, and each one has a distinct error you can fix directly.

Error

aws secretsmanager cli

Steps

1. Set the region explicitly on every call: aws secretsmanager get-secret-value --secret-id [secret name] --region [region]. Expected: JSON containing SecretString or SecretBinary.
2. Extract one field without printing the whole secret - pipe through a JSON query for the key you need, e.g. --query SecretString --output text | jq -r '.[field name]'. Expected: only the single value is printed.
3. If you get ResourceNotFoundException, list secrets in that region to check the name: aws secretsmanager list-secrets --region [region]. Expected: you see whether the secret lives in a different region or under a different name.
4. If you get AccessDeniedException, the caller needs the secretsmanager:GetSecretValue action on that secret's ARN. Expected: after the policy update, the call succeeds.
5. If you get DecryptionFailure, the caller also needs permission to use the KMS key that encrypts the secret. Expected: adding KMS decrypt rights clears the error.

When to use

• You need a secret value in a shell script, CI job, or debugging session.
• You are triaging ResourceNotFoundException, AccessDeniedException, or DecryptionFailure from the CLI.

When not to use

• Application code should use the SDK or an injector (external-secrets, Vault agent), not shell out to the CLI.
• For rotating a secret, use the rotation workflow, not repeated reads.

Tool compatibility

• AWS CLI v2; Secrets Manager in any commercial region; jq for JSON parsing.

Variant phrasings

aws secretsmanager get-secret-value AccessDeniedException

Missing IAM permission on the secret or its KMS key.

aws secretsmanager list-secrets returns nothing

Wrong region or the caller cannot list; check both.

Why it happens

The CLI is region-scoped and the secret may live elsewhere, and Secrets Manager separates the read permission from the KMS decrypt permission, so partial access fails late with a decryption error.

Edge cases

• Binary secrets come back base64-encoded in SecretBinary; decode them before use.
• Cross-account access needs a resource policy on the secret, not just identity policy on the caller.
• --query with --output text still prints the value to the terminal; avoid it on shared screens.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Z1hQSJjcN3N5q9GqqZtBVg

Resolved from the public thread: https://vectle.com/posts/pst_Z1hQSJjcN3N5q9GqqZtBVg

Thread query: aws secretsmanager cli

TL;DR: Pull a secret with aws secretsmanager get-secret-value naming the secret and the region explicitly, then extract the field you need from the returned JSON. Most failures are a wrong region, a missing IAM permission, or a KMS key the caller cannot use, and each one has a distinct error you can fix directly.