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);
Describe the feature
Amazon.Lambda.AspNetCoreServer.Hostingcurrently supports HTTP event sources, but not SQS.Could support for SQS be added, either as a new
LambdaEventSourcevalue 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.Hostingmodel. Direct SQS handling would be cleaner and avoid transport-specific limitations.Proposed Solution
Something along these lines would be useful: