aws / aws/aws-toolkit-azure-devops
LambdaNETCoreDeploy failing to upload to S3 with signature mismatch in version 5.8.1
- Dominant language
- TypeScript
- Stars
- 258
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
LambdaNETCoreDeploy in AzureDevops is throwing errors "Error uploading to xxxxx-CodeUri-Or-ImageUri-xxxxx-xxxxx.zip in bucket xxxxx/xxxxx: The request signature we calculated does not match the signature you provided. Check your key and signing method."
Looks like it started happening with Amazon.Lamda.Tools 5.8.1
**To reproduce**
Have a AzDo pipeline that wil use LambdaNETCoreDeploy to save the package to an S3 bucket.
**Your Environment**
- Azure Devops Cloud
Lambda project successfully packaged: C:\Users\VssAdministrator\AppData\Local\Temp\busTokensLambdaFunction-CodeUri-Or-ImageUri-638339604130850185.zip
Uploading to S3. (Bucket: riyo-serverless-code/busTokens Key: riyo-functions-busTokensLambdaFunction-CodeUri-Or-ImageUri-638339604130850185.zip)
Error uploading to riyo-functions-busTokensLambdaFunction-CodeUri-Or-ImageUri-638339604130850185.zip in bucket riyo-serverless-code/busTokens: The request signature we calculated does not match the signature you provided. Check your key and signing method.
##[debug]Exit code 4294967295 received from tool 'C:\Users\VssAdministrator\.dotnet\tools\dotnet-lambda.exe'
##[debug]STDIO streams have closed for tool 'C:\Users\VssAdministrator\.dotnet\tools\dotnet-lambda.exe'
##[debug]task result: Failed
##[error]Error: The process 'C:\Users\VssAdministrator\.dotnet\tools\dotnet-lambda.exe' failed with exit code 4294967295
##[debug]Processed: ##vso[task.issue type=error;]Error: The process 'C:\Users\VssAdministrator\.dotnet\tools\dotnet-lambda.exe' failed with exit code 4294967295
##[debug]Processed: ##vso[task.complete result=Failed;]Error: The process 'C:\Users\VssAdministrator\.dotnet\tools\dotnet-lambda.exe' failed with exit code 4294967295
Contributor guide
Research direction
Start with the LambdaNETCoreDeploy Azure DevOps task and the Amazon.Lambda.Tools 5.8.1 version mentioned in the report. Reproduce the pipeline upload to S3 and inspect the request-signature failure alongside the reported packaging and dotnet-lambda output. Done means the packaged Lambda artifact uploads successfully without a signature mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, typescript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100