You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't get secret through ssm with a specific name, both on Win and Linux. It looks like some internals are adding null suffix.
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
Be able to get secret with a name shared-secret-alpha through ssm
Current Behavior
I'm getting error:
aws: [ERROR]: An error occurred (ParameterNotFound) when calling the GetParameter operation: An error occurred (ParameterNotFound) when referencing Secrets Manager: Secret aws/reference/secretsmanager/shared-secret-alphanull not found.
Hi @lkurzyniec, thanks for reaching out. I wasn't able to reproduce this behavior. In my testing, I was able to successfully retrieve a SecretsManager secret with GetParameter. Could you provide debug logs of the issue? You can get debug logs by adding --debug to your command, and redacting any sensitive information. Thanks!
Thanks for your patience. I did find a couple of internal tickets reporting issues with this in eu-west-1, but I want to check a few other things as well.
Can you confirm the secret you're attempting to access is in eu-west-1?
Can you confirm whether not your secret contains a / character in the name?
Is this happening to you for all secrets in this region, or just this one in particular?
The request looks correct, and the name and region are both correct. I'm fairly convinced this is not a CLI bug, so I'm going to reach out to the SSM team for guidance on next steps.
Hi folks, I'm a member of the Parameter Store team. After doing dome digging I found that the ParameterNotFound errors in this instance were correct but the error messages themselves were less than helpful and in some cases partially mangled.
First thing to get out of the way, the null you're seeing appended to the secret name in the error messages (shared-secret-alphanull not found) is purely an error message formatting bug, not indicative of a deeper underlying problem. We're fixing that.
The shared-secret-alpha calls failed because the secret has no version carrying the AWSCURRENT staging label. Secrets Manager resolved the name but had no current version to return. The most likely cause is a secret created without supplying a value, or maybe a rotation that left AWSCURRENT unassigned. Try running aws secretsmanager describe-secret --secret-id shared-secret-alpha and check VersionIdsToStages for whether anything maps to AWSCURRENT. In this case, Parameter Store was right to throw ParameterNotFound but the error message text wasn't differentiating between a secret that doesn't exist vs a secret without a default version. We're also working on a fix for that so that the ParameterNotFound error you get from parameter store relays the original Secrets Manger error so that you can disambiguate between this case vs the secret not existing at all.
From our logs:
ParameterNotFound: An error occurred (ParameterNotFound) when referencing Secrets Manager: Secret aws/reference/secretsmanager/shared-secret-alphanull not found.
Caused by: com.amazonaws.services.secretsmanager.model.ResourceNotFoundException: Secrets Manager can't find the specified secret value for staging label: AWSCURRENT
The alpha secret error responses appear to be valid, with no secret named alpha existing in the account at the time.
From our logs:
ParameterNotFound: An error occurred (ParameterNotFound) when referencing Secrets Manager: Secret aws/reference/secretsmanager/alphanull not found.
Caused by: com.amazonaws.services.secretsmanager.model.ResourceNotFoundException: Secrets Manager can't find the specified secret.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Activity
RyanFitzSimmonsAK commentedon Aug 4, 2026
Hi @lkurzyniec, thanks for reaching out. I wasn't able to reproduce this behavior. In my testing, I was able to successfully retrieve a SecretsManager secret with
GetParameter. Could you provide debug logs of the issue? You can get debug logs by adding--debugto your command, and redacting any sensitive information. Thanks!lkurzyniec commentedon Aug 6, 2026
@RyanFitzSimmonsAK
lkurzyniec commentedon Aug 24, 2026
@RyanFitzSimmonsAK any news?
RyanFitzSimmonsAK commentedon Sep 22, 2026
Thanks for your patience. I did find a couple of internal tickets reporting issues with this in
eu-west-1, but I want to check a few other things as well.eu-west-1?/character in the name?lkurzyniec commentedon Sep 23, 2026
@RyanFitzSimmonsAK answering:
eu-west-1/chararn:aws:secretsmanager:eu-west-1:5***8:secret:shared-config-dev-XXnnGRshared-config-alpha, but not working forshared-secret-alphaSome more examples:

RyanFitzSimmonsAK commentedon Sep 23, 2026
2026-08-06 13:00:26,535 - MainThread - botocore.endpoint - DEBUG - Making request for OperationModel(name=GetParameter) with params: {'url_path': '/', 'query_string': '', 'method': 'POST', 'headers': {'X-Amz-Target': 'AmazonSSM.GetParameter', 'Content-Type': 'application/x-amz-json-1.1', 'User-Agent': 'aws-cli/2.36.17 md/awscrt#0.36.0 ua/2.1 os/linux#6.18.33.2-microsoft-standard-WSL2 md/arch#x86_64 lang/python#3.14.6 md/pyimpl#CPython m/s,r,Z,E,b cfg/retry-mode#standard md/installer#script-exe sid/xxx md/distrib#ubuntu.24 md/prompt#off md/command#ssm.get-parameter'}, 'body': b'{"Name": "/aws/reference/secretsmanager/alpha", "WithDecryption": true}', 'url': 'https://ssm.eu-west-1.amazonaws.com/', 'context': {'client_region': 'eu-west-1', 'client_config': <botocore.config.Config object at 0x78850220f110>, 'has_streaming_input': False, 'auth_type': None, 'unsigned_payload': None, 'auth_options': ['aws.auth#sigv4']}}The request looks correct, and the name and region are both correct. I'm fairly convinced this is not a CLI bug, so I'm going to reach out to the SSM team for guidance on next steps.
Ticket # for internal use : P519737792
ivanatpr commentedon Sep 29, 2026
Hi folks, I'm a member of the Parameter Store team. After doing dome digging I found that the ParameterNotFound errors in this instance were correct but the error messages themselves were less than helpful and in some cases partially mangled.
First thing to get out of the way, the
nullyou're seeing appended to the secret name in the error messages (shared-secret-alphanull not found) is purely an error message formatting bug, not indicative of a deeper underlying problem. We're fixing that.The
shared-secret-alphacalls failed because the secret has no version carrying theAWSCURRENTstaging label. Secrets Manager resolved the name but had no current version to return. The most likely cause is a secret created without supplying a value, or maybe a rotation that leftAWSCURRENTunassigned. Try runningaws secretsmanager describe-secret --secret-id shared-secret-alphaand checkVersionIdsToStagesfor whether anything maps toAWSCURRENT. In this case, Parameter Store was right to throw ParameterNotFound but the error message text wasn't differentiating between a secret that doesn't exist vs a secret without a default version. We're also working on a fix for that so that the ParameterNotFound error you get from parameter store relays the original Secrets Manger error so that you can disambiguate between this case vs the secret not existing at all.From our logs:
alphasecret error responses appear to be valid, with no secret namedalphaexisting in the account at the time.From our logs:
lkurzyniec commentedon Sep 30, 2026
@ivanatpr @RyanFitzSimmonsAK thank you both for your investigation.
This is it. I wish I have it in error messages then I would know what is missing, what needs to be fixed.
github-actions commentedon Sep 30, 2026
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.