fix(bedrock-agentcore-alpha): self-managed memory strategy validation throws on unresolved tokens

[mazyu36]

Issue # (if applicable)

None

Reason for this change

The validation in SelfManagedMemoryStrategy throws when unresolved CDK tokens (e.g. CfnParameter.valueAsNumber) are passed for historicalContextWindowSize or the triggerConditions fields. These values can't be checked at synth time and should be skipped.

Description of changes

Added Token.isUnresolved() / Duration.isUnresolved() guards in self-managed-strategy.ts, following the same pattern as _validateMemoryExpirationDays (memory.ts) and validateLifecycleConfiguration (runtime.ts). Same approach as #37197.

Describe any new or updated permissions being added

None.

Description of how you validated changes

Added unit tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[mazyu36]

Exemption Request: This change only adds synth-time token guards to existing validation logic; the runtime behavior and generated CloudFormation are unchanged, so an integration test would not exercise anything that unit tests don't already cover.

[aws-cdk-automation]

(This review is outdated)

[leonmk-aws]

Thank you for your contribution!

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-28 16:03 UTC · Rule: default-squash
• 🚫 Left the queue — 2026-04-28 16:04 UTC · at 9682c71f8dff0ac5f1f8a1ac10c493436b8f769c

This pull request spent 11 seconds in the queue, with no time running CI.

Reason

The pull request can't be updated

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/pr-issue-check.yml without workflows permission

Hint

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mazyu36]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

Details

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/pr-issue-check.yml without workflows permission

[mazyu36]

@Mergifyio requeue

[mergify]

requeue

☑️ Command disallowed due to command restrictions in the Mergify configuration.

Details

• sender-permission >= write

Pull request has been modified.

[mazyu36]

@leonmk-aws
Thanks. Could you approve again?

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-30 08:23 UTC · Rule: default-squash
• ✅ Checks passed · in-place
• ✅ Merged — 2026-04-30 08:52 UTC · at b2c29a6eebd348ed45490fdda5be48b915a28227 · squash

This pull request spent 29 minutes 11 seconds in the queue, including 28 minutes 53 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(bedrock-agentcore-alpha): self-managed memory strategy validation throws on unresolved tokens #37691
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(bedrock-agentcore-alpha): self-managed memory strategy validation throws on unresolved tokens #37691
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.