Skip to content

docs: clarify CDK asset deployment requirements #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
quetzalliwrites merged 2 commits into from
Dec 29, 2025
Merged

docs: clarify CDK asset deployment requirements #372

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b52af26
Clarify CDK Asset deployment requirements
quetzalliwrites Dec 24, 2025
d7cfc00
Apply suggestion from @quetzalliwrites
quetzalliwrites Dec 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion src/content/docs/aws/integrations/aws-native-tools/aws-cdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,13 @@ awslocal sns list-topics

Updating CDK stacks may result in deployment failures and inconsistent state within LocalStack.
It is advisable to prioritize re-creating (deleting and re-deploying) over updating stacks.
Our focus for this year will be on resolving issues related to the `UPDATE` support, and continuous improvements can be anticipated in this area throughout 2024.
Copy link
Collaborator Author

@quetzalliwrites quetzalliwrites Dec 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is out of date, from 2024.


Copy link
Collaborator Author

@quetzalliwrites quetzalliwrites Dec 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we're moving away from the term PRO, used the phrase 'paid plan." Would appreciate feedback on whether this is the right approach. 😸

:::note

CDK Asset deployment (e.g., Lambda code, S3 content) requires a LocalStack paid plan.

This process relies on the `AWS::CloudFormation::CustomResource` API, which is not available in the Community edition. If deployments hang or fail silently, check the LocalStack logs for `CustomResource` errors.
:::

### Stacks with validated certificates

Expand Down