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.

Context: 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.

## Matched source
Source: Stack Overflow question: https://stackoverflow.com/questions/57821886/aws-secrets-manager-can-t-find-the-specified-secret
Original query: "AWS Secrets Manager can't find the specified secret (AWS Secrets Manager)"
Key terms: find, manager, secret, secrets, specified