aws / aws/aws-toolkit-visual-studio

"Upload Lambda Function" Execution Memory (MB): limited to 3008, why not 10240?

Open
#181 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
135
Forks
37
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Unable to set Memory for Lambda function to the max of 10240MB, I can only use the old maximum of 3008MB. Setting to 10240MB via aws-lambda-tools-defaults.json and then publishing causes Visual Studio to crash.

**To Reproduce**
Steps to reproduce the behavior
C# project.
Right click on project, select "Publish to AWS Lambda...".
"Upload Lambda Function" dialogue comes up
Click "Next"
Second page comes up with, amongst other things, "Execution, Memory (MB):"
Click the drop down to select the memory, the maximum amount is 3008.
If I go to AWS Console, I can update the Memory to 10240.
If I try to set the Memory to 10240 in the aws-lambda-tools-defaults.json Visual Studio crashes.

**Expected behavior**
I should be able to set to 10240 in the drop down or the aws-lambda-tools-defaults.json file.

**Screenshots**

**Computer (please complete the following information):**

- Windows Version: 10 20H2
- Visual Studio Version: Community 2018 v 16.11.5
- AWS Toolkit for Visual Studio Version: 1.22.0.0

**Additional context**

Contributor guide

Open the contributing guide

Research direction

Start with the "Upload Lambda Function" dialog and the aws-lambda-tools-defaults.json handling in a C# project. Reproduce the 3008 MB limit and the crash when 10240 is configured; done means the dialog and configuration accept 10240 MB without Visual Studio crashing.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, csharp
Domain
cloud, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.