Convox still using Node 16.x on AWS Lambda

Hi,

We recently updated our racks to use Node.js v20 as <= 18 is deprecated. However, in our AWS account we still have two Lambda functions/apps that are stuck on Node v16, and we’re not sure how to update them, or really even how they are used with Convox?

The Lambda functions in question each belong to a Lambda application that is a resource in a CloudFormation stack that also includes a role that I think is used for Convox Console. However, the role for one of these stacks hasn’t been accessed in a very long time, and the other one has “test” in the name – suggesting maybe when we originally set up Convox Console long ago, perhaps we ended up creating two Console connections somehow?

What’s the next step for updating Node for these stacks, and is there any way we can confirm for certain which ones (if any) can be deleted/are unused?

Is there a way to re-connect Convox Console to our AWS account if we were to delete the wrong role?