feat: add streamDeliveryResources schema, CLI flags, and validation for memory record streaming#531
Merged
Hweinstock merged 3 commits intoaws:mainfrom Apr 8, 2026
Conversation
Hweinstock
changed the title
Hweinstock
force-pushed
the
feature/stream-delivery-resources
branch
from
d1bb32b to
bfede65
Compare
Hweinstock
force-pushed
the
feature/stream-delivery-resources
branch
from
bfede65 to
001b33b
Compare
Hweinstock
force-pushed
the
feature/stream-delivery-resources
branch
from
001b33b to
12741cd
Compare
Hweinstock
changed the title
15 tasks
…or memory record streaming
- Replace unsafe `as MemoryStrategyType` casts with Zod parse - Include deliveryType in streamDeliveryResources conflict check - Reject deliveryType without dataStreamArn - Validate streamDeliveryResources JSON eagerly in validator - Include Zod error details in parseStreamDeliveryResources - Extract DEFAULT_DELIVERY_TYPE constant - Tighten createMemory strategies param type
Hweinstock
force-pushed
the
feature/stream-delivery-resources
branch
from
12741cd to
8202106
Compare
Contributor
Package TarballHow to installnpm install https://github.com/aws/agentcore-cli/releases/download/pr-531-tarball/aws-agentcore-0.6.0.tgz |
CUSTOM is not a valid MemoryStrategyType. The previous test relied on an unsafe `as` cast to pass an invalid strategy through. Now that we use Zod parse, invalid strategies are correctly rejected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
NOTE: Do not merge, dependent on unreleased CDK changes.
Description
Problem
Customers have no way to receive real-time notifications when memory records change, forcing them to poll APIs to detect new data.
Solution
Added streamDeliveryResources support to agentcore add memory, allowing customers to configure push-based delivery of memory record events to a target (e.g. Kinesis Data Stream).
Depends on a corresponding CDK construct change.
Related Issue
Closes #528
Documentation PR
N/A
Type of Change
Testing
How have you tested the change?
I ran
npm run test:unitandnpm run test:integI ran
npm run typecheckI ran
npm run lintIf I modified
src/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsagentcore add memorywith --data-stream-arn and --stream-content-level flat flags — config written correctly to agentcore.jsonagentcore add memorywith --stream-delivery-resources inline JSON — config written correctlyagentcore deploy— stack deployed successfully and created memories with streams.Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.