aws-samples / aws-samples/aws-lambda-environmental-variables-from-aws-secrets-manager
.Net fails to start
- Dominant language
- Shell
- Stars
- 38
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Hi All,
I implemented this solution with a node test script that displays the environment variables with no issues.
We have a .NET runtime for which we are implementing these to fix exposed secrets issues. But once the wrapper executes the .Net runtime startup errors out with no reason specified.
These are the Lambda logs:
INIT_START Runtime Version: dotnet:core3.1.v14 Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:7cbb73ab7c13b31a3c81dc02f85a149ca730c142e4f3b99100ec0594932d6ba0
No new layer was specified, unsetting AWS_LAMBDA_EXEC_WRAPPER
[WARN] (invoke@invoke.c:331 errno: None) run_dotnet(dotnet_path, &args) failed
RequestId: 3319b38f-cc58-4063-8af3-430c969679df Error: Runtime exited without providing a reason
Runtime.ExitError
The Lambda function without this getSecret layer works successfully.
Any guidance will be greatly appreciated.
Contributor guide
Research direction
Start by reproducing the failure with the .NET Core 3.1 Lambda runtime and the getSecret layer, then compare its startup logs with the working Node test script. Use the reported Lambda logs and wrapper behavior to identify why the runtime exits without a reason; done means the .NET function starts successfully with the layer and no longer reports Runtime.ExitError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- backend, cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100