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
where NAME is the full name of an SSM param, e.g /my/best/ssm/ever with SecureString set as type
Reproduction Steps
// credentials must be in env - locally I use AWS_PROFILE with AWS_REGION, and in AWS, I use the lambda envfuncmain(){
ctx:=context.Background()
cfg, err:=config.LoadDefaultConfig(ctx)
iferr!=nil {
log.Fatalf("unable to load SDK config, %v", err)
}
ssmClient:=ssm.NewFromConfig(cfg)
ssmValue, err:=ssmClient.GetParameter(ctx, &ssm.GetParameterInput{
Name: aws.String("/my/best/ssm/ever"),
WithDecryption: aws.Bool(true),
})
iferr!=nil {
log.Fatalf("unable to get \"%s\", with error: %v", envValue, err)
}
// expecting to have a valid ssmValue at this point, but `err != nil`
Using the AWS CLI with the same profile locally or in the AWS account returns a valid SSMParameter with the requested name.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
So after updating my AWS SDK dependencies to the following, for some reason SSM.GetParameter is not working anymore
Dependencies new:
Dependencies old:
Expected Behavior
should work for existing ssm params, when account has access to them.
Current Behavior
where NAME is the full name of an SSM param, e.g
/my/best/ssm/ever
withSecureString
set as typeReproduction Steps
Using the AWS CLI with the same profile locally or in the AWS account returns a valid SSMParameter with the requested name.
Possible Solution
I had to downgrade back to
Additional Information/Context
AWS Go SDK V2 Module Versions Used
Compiler and Version used
go1.21.3
Operating System and version
darwin/arm64
The text was updated successfully, but these errors were encountered: