←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.2s | source
Show context
totality ◴[] No.42140060[source]
I'm on the AWS Amplify team and wanted to give folks an update. First off, definitely empathize with the pain that Elliot went through. The referenced blog post is part of our advanced extensibility documentation, which covers how customers can use AWS CDK to add features that are not directly supported by the Amplify tooling, such as integrating with OpenSearch. Our initial OpenSearch extensibility documentation did not include the removalPolicy config, which led to the issues Elliot experienced. To mitigate this, we updated our documentation to include `removalPolicy: RemovalPolicy.DESTROY` for all stateful extensibility resources, ensuring they are cleaned up when the stack is deleted. Additionally, we will be updating the default behavior for `npx ampx sandbox` and `npx ampx pipeline-deploy` to apply this removal policy.
replies(1): >>42186527 #
1. myroon5 ◴[] No.42186527[source]
CDK changing default removalPolicies was obviously problematic years ago:

https://github.com/aws/aws-cdk/issues/12563#issuecomment-771...

Another implicit surprise under the hood of CDK