Skip to content

feature: bedrock agent api support#2019

Closed
martinsafsten wants to merge 2 commits intoaws:masterfrom
martinsafsten:bedrock-agent-api
Closed

feature: bedrock agent api support#2019
martinsafsten wants to merge 2 commits intoaws:masterfrom
martinsafsten:bedrock-agent-api

Conversation

@martinsafsten
Copy link
Copy Markdown

@martinsafsten martinsafsten commented Mar 19, 2025

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:

  • Created a new events project for bedrock agent event contracts: Amazon.Lambda.BedrockAgentEvents
  • Added new LambdaEventSource in Amazon.Lambda.AspNetCoreServer.Hosting: BedrockAgentApi
  • Added request and response marshalling for Amazon Bedrock agents in Amazon.Lambda.AspNetCoreServer when using the new event source.
  • Unit tests against the TestWebApi to verify correct marshalling.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@martinsafsten martinsafsten changed the title Bedrock Agent API support feature: bedrock agent api support Mar 19, 2025
@martinsafsten
Copy link
Copy Markdown
Author

@ashishdhingra any updates on this?

@ashishdhingra
Copy link
Copy Markdown
Contributor

@martinsafsten We have the issue in our backlog and our team would soon look into it based on priority. Thanks for your patience.

@normj
Copy link
Copy Markdown
Member

normj commented May 7, 2026

Sorry for never getting back to you sooner. With the speed of change in the AI space I'm leery of putting a dependency on Bedrock Agents with our ASP.NET Core libraries. I'm not on the Bedrock team and don't speak for their roadmap but my read is the direction is moving a lot more towards AgentCore then the original Bedrock Agents service. So if we tangle Bedrock Agents with ASP.NET Core libraries we might regret that decision in the next year.

I'm going to close the PR because I can't see us acting on it unless we see a different direction between Bedrock Agents vs AgentCore.

@normj normj closed this May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants