Queues not listed in Monitor Dead Letter Queue page in Lambda Test Tool.

[mwleinad]

Describe the bug

I might just be missing something but then going to
http://localhost:5050/monitor-dlq

I'm getting this error
Error listing queues: Value cannot be null. (Parameter 'Options property cannot be empty: ClientName')

Expected Behavior

Queues should be listed

Current Behavior

Queue list is empty

Reproduction Steps

Open the http://localhost:5050/monitor-dlq
btw, this is a executable assemblies, does that have anything to do?

Possible Solution

I can't find a way to specify the client name and the code doesn't look to take clientname into account anywhere.

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSSDK V3

Targeted .NET Platform

.NET 6

Operating System and version

Windows 10

[ashishdhingra]

Hi @mwleinad,

Good afternoon.

Thanks for reporting the issue. I tried reproducing the issue using below steps:

• Created Lambda function developed using the Top Level statements (executable assembly) and deployed the same to AWS Lambda.
• Used article https://dev.classmethod.jp/articles/how-to-handle-failure-in-aws-lambda-using-dlq-mechanism-and-setup/ as reference, for setting up DLQ for Lambda function created above.
• Followed steps in Missing documentation on running AOT lambdas in test tool #1539 (comment) to use Lambda Test Tool with executable assembly project.
• On Lambda function developed using the Top Level statements (executable assembly). page:
  • Selected the SQS queue from the drop down.
  • Started monitoring the queue.

The messages were successfully displayed in the table:

Just a note, I did not use SSO profile during testing. Once I selected configured SSO profile from dropdown (even after aws sso login --profile <<profile-name>>, I got the error Error listing queues: Value cannot be null. (Parameter 'Options property cannot be empty: ClientName').

Looking at the error message shared by you in issue description, it appears you might be using the SSO profile. Could you please confirm? If yes, are you logged in to your SSO profile using AWS CLI aws sso login?

I do see that Amazon.Lambda.TestTool.csproj has reference to AWSSDK.Core and AWSSDK.SQS version 3.7.0. There was a similar SSO issue reported in .NET SDK which was fixed in later version is SDK. So in this case, once you confirm that you are using SSO profile, we might need to just update AWSSDK package references in Lambda Test Tool to latest versions.

Thanks,
Ashish

[github-actions]

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[ashishdhingra]

Fixed in Amazon Lambda TestTool version 0.14.1.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.