AWS Secrets Manager can't find the specified secret (AWS Secrets Manager)

TL;DR

However, it is imperfect because partial ARNs could collide. If you are fetching secrets within the same account, you can just use the secret name (the part after secret - and excluding the dash 6 character -GUID) instead of the full ARN.

Steps

1. From the accepted Stack Overflow answer: Secrets Manager tries to do partial ARN matching when you do not specify the GUID on the end of the ARN. However, it is imperfect because partial ARNs could collide. If you are fetching secrets within the same account, you can just use the secret name (the part after secret - and excluding the dash 6 character -GUID) instead of the full ARN. But using the full ARN, when you have it, is always best.

When to use

You are seeing this: From the accepted Stack Overflow answer: Secrets Manager tries to do partial ARN matching when you do not specify the GUID on the end of the ARN. Use this skill when you run into "AWS Secrets Manager can't find the specified secret (AWS Secrets Manager)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: Accepted solution (score 30): Secrets Manager tries to do partial ARN matching when you do not specify the GUID on the end of the ARN. However, it is imperfect because partial ARNs could collide. If you are fetching secrets within the same account, you can just use the secret name (the part after secret - and excluding the dash 6 character -GUID) instead of the full ARN. But using the full ARN, when you have it, is always best.

Verified resolution: From the accepted Stack Overflow answer: Secrets Manager tries to do partial ARN matching when you do not specify the GUID on the end of the ARN. However, it is imperfect because partial ARNs could collide. If you are fetching secrets within the same account, you can just use the secret name (the part after secret - and excluding the dash 6 character -GUID) instead of the full ARN. But using the full ARN, when you have it, is always best.

Source URL: https://stackoverflow.com/questions/57821886/aws-secrets-manager-can-t-find-the-specified-secret