# CI/CD Issue for Node 18.x Runtime

**URL:** <https://forum.serverless.com/t/ci-cd-issue-for-node-18-x-runtime/18211>\
**Category:** Serverless Framework\
**Tags:** aws, lambda\
**Created:** [January 19, 2023, 5:59pm UTC](https://forum.serverless.com/t/ci-cd-issue-for-node-18-x-runtime/18211 "2023-01-19T17:59:26Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![gourabb8273](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/gourabb8273/32/7550_2.png) [@gourabb8273](https://forum.serverless.com/u/gourabb8273)\
**Post date:** [August 2, 2023, 7:23pm UTC](https://forum.serverless.com/t/ci-cd-issue-for-node-18-x-runtime/18211/11 "2023-08-02T19:23:09Z")

</div>

> [@mojoalan](#):
>
> So you can continue using aws-sdk v2 while increasing the provider/runtime to nodejs18.

Hi, As you said I have upgraded serverless till 3.32.2 also downgraded aws sdk till version 2 and using nodejs 18 as a runtime provider. Every thing was looking fine initially but now getting some issue in lambda while calling as below.

\*\*Uncaught exception \*\*  
**error**  
**The security token included in the request is invalid**

We have identified this issue seems coming from serverless. we did some syntax level changes as well like \* `provider.role` → `provider.iam.role` but still not working and issue is coming.

Sharing some similar thread I found on internet

> [@Serverless Error - The security token included in the request is invalid](https://forum.serverless.com/t/serverless-error-the-security-token-included-in-the-request-is-invalid/2219/4):
>
> In my case I am on aws sso credentials. It is refreshed. The ~/.aws/credentials is up to date which includes a token. I understand serverless looks there and ignores ~/.aws/config. But it does not work with --aws-profile or without it but with sls config credentials either. Very annoying. Strange thing is it was working fine 12 hours ago and today there is no luck at all.

> <https://stackoverflow.com/questions/53344944/serverless-error-the-security-token-included-in-the-request-is-invalid>

Here I am using role base acces so not using aws access and secret key.  
Could you please help me out how to fix it?

---

_[View the full topic](https://forum.serverless.com/t/ci-cd-issue-for-node-18-x-runtime/18211)._