Support SQS event sources in Amazon.Lambda.AspNetCoreServer.Hosting

[irunjic]

Describe the feature

Amazon.Lambda.AspNetCoreServer.Hosting currently supports HTTP event sources, but not SQS.

Could support for SQS be added, either as a new LambdaEventSource value or via a custom event source adapter/extensibility model?

Use Case

We have an ASP.NET Core Lambda application that exposes HTTP endpoints and also needs to process SQS workflow messages.

The only reason we currently route SQS messages through an HTTP hop (with EventBridge pipe) is to stay within the Amazon.Lambda.AspNetCoreServer.Hosting model. Direct SQS handling would be cleaner and avoid transport-specific limitations.

Proposed Solution

Something along these lines would be useful:

builder.Services.AddAWSLambdaHosting(LambdaEventSource.HttpApi);
builder.Services.AddAWSLambdaHosting(LambdaEventSource.Sqs);

[afroz429]

Thanks for the feature request, @irunjic. We'll review this with the team and get back to you.

[GarrettBeatty]

Hi @irunjic thanks for opening this issue. Curious how you are thinking on mapping an SQS event to an http endpoint? for For httpapi -> http there is a pretty direct mapping. but sqs -> http im not really sure what it would be/what would make sense? I dont think this package is meant for that use case.

Why not directly process the SQS messages with a regular lambda function?

[github-actions]

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.