AWS Toolkit has only 3 node choices for Runtime - no dotnet, python etc.

Question

I created an empty Lambda function in .Net 8 in JetBrains Rider. I am able to debug and run it using the Mock Lambda Test Tool. All seems well until I want to push it to the cloud.

When I right-click Lambda and choose "Create New AWS Lambda..." in the IDE, I only see `nodejs16.x`, `nodejs18.x` and `nodejs20.x`. How do I get the `dotnet8` (or any other runtime values) to show up in there? What is odd is that there are other functions deployed to our AWS instance that were done by another dev in python. When I right-click on them, I can shoose "Update Configuration" and the drop-down for runtime is completely full of all the alternatives... 38 options including the dotnet6 and 8.

Also - making my problem somewhat moot, you can use the command line `dotnet lambda deploy-function` to deploy it, and it properly uses dotnet8 and then it shows up in the update configuration dialog.

What gives with the GUI? I updated everything today with the latest.

![Enter image description here](/media/postImages/original/IMylTzq4fBRpq4JnZWWvpo-A)

I do have a aws-lambda-tools-defaults.json file.

```
{
  "Information": [  "This file ... ],
  "profile": "default",
  "region": "us-east-1",
  "configuration": "Release",
  "function-architecture": "arm64",
  "function-runtime": "dotnet8",
  "function-memory-size": 512,
  "function-timeout": 30,
  "function-handler": "MySampleSqsApp::MySampleSqsApp.Function::FunctionHandler"
}
```

Answer

It sounds like you're encountering a discrepancy between the runtime options available in the AWS Toolkit for Rider and those available through other methods like the AWS CLI or directly in the AWS Management Console.

There could be a few reasons why you're seeing only Node.js runtimes in the AWS Toolkit for Rider:

1. **Missing AWS Lambda Runtimes**: It's possible that the AWS Toolkit for Rider hasn't been updated to include all available Lambda runtimes. This could be due to a delay in updating the toolkit to support newer runtimes like .NET 8.

2. **Configuration Issue**: There may be a configuration issue with your AWS Toolkit for Rider installation that's causing it to not recognize or display certain Lambda runtimes.

3. **IDE Integration Issue**: There could be an integration issue between JetBrains Rider and the AWS Toolkit specifically related to runtime selection.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. **Update AWS Toolkit for Rider**: Make sure you have the latest version of the AWS Toolkit for Rider installed. Check for any available updates and install them if necessary.

2. **Check AWS Toolkit Configuration**: Review the configuration settings in the AWS Toolkit for Rider to ensure they are correctly set up, including AWS credentials and region settings.

3. **File Bug Report**: If you're confident that the AWS Toolkit for Rider should support .NET 8 and other runtimes but they're not showing up, consider filing a bug report with JetBrains or the AWS Toolkit team to investigate the issue further.

4. **Use Command-Line Deployment**: As you mentioned, you can use the `dotnet lambda deploy-function` command-line tool to deploy your Lambda function with the desired runtime. This is a valid workaround until the issue with the AWS Toolkit for Rider is resolved.

5. **Seek Community Support**: Reach out to other users of the AWS Toolkit for Rider or JetBrains Rider forums to see if anyone else has encountered similar issues and found a solution.

By taking these steps, you should be able to either resolve the issue with the AWS Toolkit for Rider or find an alternative method for deploying your Lambda functions with the desired runtime.

AWS Toolkit has only 3 node choices for Runtime - no dotnet, python etc.

Relevant content