fix(custom-resource-handlers): deployment fails when parameter already exists

[otaviomacedo]

In the upgrade to 2.253.0, there is a scenario in which the SSM parameters used by the custom resources are not deleted, even though the custom resources themselves are. When upgrading to 2.253.1, the custom resources are recreated, and the writer tries to put the parameter again. But, since it's not passing the Overwrite: true parameter, SSM rejects the request, and the deployment fails.

Add Overwrite: true to the putParameter call.

Fixes #37845.

---

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

[github-actions]

⚠️ This pull request description does not follow the correct template structure.

PRs without a linked issue will receive lower priority for review and merging. Please update the description to follow the PR template and include a line like Closes #123 in the Issue section. If no existing issue matches your change, create one first.

[aws-cdk-automation]

(This review is outdated)

[alvazjor]

LGTM

✅ 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-05-13 06:12 UTC · Rule: default-squash
• ✅ Checks passed · in-place
• ✅ Merged — 2026-05-13 06:59 UTC · at 8641c870ecd24edb3c40d1cee7fc76dc084131ee · squash

This pull request spent 47 minutes 13 seconds in the queue, including 46 minutes 56 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(custom-resource-handlers): deployment fails when parameter already exists #37852
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(custom-resource-handlers): deployment fails when parameter already exists #37852
• 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.