What happened
AWS published guidance on using Amazon Bedrock AgentCore to let agents in one AWS account generate answers from an Amazon Bedrock knowledge base in another account.
The knowledge base is backed by Amazon Redshift Serverless, and the design avoids copying source data between accounts.
The post explains the architecture and security boundary, then covers two orchestration models: a code-based Strands agent and a declarative AgentCore harness.
Why it matters
This approach supports organizations that need to keep data in one account while enabling agents in other accounts to use it, which can simplify data governance and reduce duplication.
Presenting two orchestration models gives teams flexibility: one path is code-driven, the other is declaration-based, so builders can choose the style that fits their workflow.
Key facts
Amazon Bedrock AgentCore agents in one account can generate answers from a knowledge base located in another account.
The knowledge base is backed by Amazon Redshift Serverless.
Source data is not copied between accounts.
The post covers architecture, security boundary, and two orchestration models: a code-based Strands agent and a declarative AgentCore harness.
What to watch next
Further detail on how the security boundary is configured could clarify how permissions and data access are enforced across accounts.
It may be useful to see guidance on when to choose the code-based Strands agent versus the declarative AgentCore harness for different use cases.