Get parameter synchronously for v3 aws-sdk

[anilgarg88]

I am using aws-sdk/client-ssm library for v3 version of aws-sdk. I am calling function get parameter but it is calling asynchronously. Is there any synchronous way of getting parameter for new javascript v3 syntax and library because aws-sdk is going out of support in dec2023. And we are getting errors or warnings for this library.

[RanVaknin]

Hi @anilgarg88,

In both JS SDK v2, and v3 the only way to make service calls is asynchronously.
I'm not sure what implementation you are trying to replace in v2 that does not exist in v3?

You can Synchronous "looking" code by running operations with Async / Await however its not truly synchronous.

If I can get more context about your use case I might be able to provide a solution for you.
Thanks,
Ran~

[anilgarg88]

my sample code is as below this is a lambda function : ->

const aws = require("@aws-sdk/client-ssm");
const ssm = new aws.SSM({ region: 'eu-west-2' })
let parameter = await ssm.getParameter({ Name: `/${tenv}/${serviceName}/API_KEY` ,WithDecryption: true });
process.env.API_KEY = parameter.Parameter.Value;
console.log(process.env.API_KEY);

The problem with this code is its asynchronous nature. the function definition initialises first and then this ssm function gets executed. my lambda function invocation fails because this environment variable is not available. so basically i need to load all ssm parameters before anything happens on a lambda. previously aws-param-store getParamtersync method was used.

[RanVaknin]

Hi @anilgarg88,

Im not really familiar with aws-param-store. But using a 3rd party tool to manage AWS secrets is probably not the best solution.

the function definition initialises first and then this ssm function gets executed. my lambda function invocation fails because this environment variable is not available.

Are you sure about this?
From what I can see you are telling the SDK: "fetch me this secret so I can then use to call the SDK with" Which obviously will cause an error.
You need to run your lambda with your credentials already wired up to make calls to the SDK (those env variables need to be injected before the function fires) you can learn more about how to do that by following this documentation.

Let me know if you have any other questions.
Thanks,
Ran~

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.