feature: bedrock agent api support #2019
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: #2007
Description of changes:
I added support for building a .NET Core Web Api with Amazon.Lambda.AspNetCoreServer.Hosting, and use it as a Amazon Bedrock Action Group Lambda Function, configured with a OpenAPI specification. The user simply calls
IServiceCollection.AddAWSLambdaHosting(LambdaEventSource.BedrockAgentApi)
, in the same manner as the existing event sources, which loads up the correct request and response handling.I have not created a change file. Awaiting a review to see if the general strategy is accepted.
Here is a structured list of the changes:
Amazon.Lambda.BedrockAgentEvents
Amazon.Lambda.AspNetCoreServer.Hosting
: BedrockAgentApiAmazon.Lambda.AspNetCoreServer
when using the new event source.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.