Editing Lambda in VS Code using the AWS Console - Can the location files are stored be changed?
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
Mac OS Info:
- Chip: Apple M4 Max
- Memory: 48 GB
- OS: 15.5 (24F74)
VS Code Info:
- Version: 1.102.1 (Universal)
- Commit: 7adae6a56e34cb64d08899664b814cf620465925
- Date: 2025-07-15T16:41:17.147Z (1 wk ago)
- Electron: 35.6.0
- ElectronBuildId: 11847422
- Chromium: 134.0.6998.205
- Node.js: 22.15.1
- V8: 13.4.114.21-electron.0
- OS: Darwin arm64 24.5.0
## Question
When I download lambdas from the "Open in Visual Studio Code" button in the AWS console to edit locally, they are stored in the location "/tmp/aws-toolkit-vscode/lambda/" followed by the region and function name. Is it possible to change this location?
Contributor guide
Research direction
Start by searching the extension for the /tmp/aws-toolkit-vscode/lambda/ path and trace the code used by the AWS Console's "Open in Visual Studio Code" action. Determine whether an existing setting controls the location; done means the storage location can be changed and the supported configuration is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, vscode
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100