You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 27, 2026. It is now read-only.
Currently, it's possible to casually delete the the critical data within the S3 Bucket and OpenSearch Domain via the AWS Console or APIs. By updating their policies to protect them from deletion, we can make it less likely they will be deleted by accident. For reference, it's possible to delete these resources using the CLI's destroy-cluster command, but only if the --destroy-everything flag is also passed (otherwise they are left in the user's account while the other resources are torn down).
Acceptance Criteria
OpenSearch Domain and S3 Bucket protected from deletion via policy
destroy-cluster code updated to work with this new factor
Description
Currently, it's possible to casually delete the the critical data within the S3 Bucket and OpenSearch Domain via the AWS Console or APIs. By updating their policies to protect them from deletion, we can make it less likely they will be deleted by accident. For reference, it's possible to delete these resources using the CLI's
destroy-clustercommand, but only if the--destroy-everythingflag is also passed (otherwise they are left in the user's account while the other resources are torn down).Acceptance Criteria
destroy-clustercode updated to work with this new factor