AWS Policy to cleanup unattached volumes deleted 'restartable workspaces'?

It's possible to have an AWS policy which removes EBS volumes that are not attached to EC2 instances. Is this dangerous to my restartable workspace?

I cannot resume my Workspace, there is a error on PVC missing?

I would like to save AWS fees by removing unused EBS Volumes?

Restartable Workspaces will unmount the volume and remain 'Bound'. This however may fall within AWS cleanup policies of 'unattached' volumes. If you remove a Workspace volume, it may cause dataloss for the user if there are 'unsynced' files on the PVC.

To avoid this, create tags/labels and exclude the Domino Volumes. This required Domino 5.X!

% helm list -A | grep aws
aws-ebs-csi-driver          	domino-platform	1       	2022-01-06 01:46:42.427851259 +0000 UTC	deployed	aws-ebs-csi-driver-2.2.1-0.0.3     	1.3.0
aws-efs-csi-driver          	domino-platform	1       	2022-01-06 01:46:42.430041096 +0000 UTC	deployed	aws-efs-csi-driver-2.2.0-0.2.1     	1.3.3

Then find the deployment in the domino-platform namespace. Edit the deployment:

kubectl edit deployment aws-ebs-csi-driver-controller -n domino-platform

Added a new “foo=bar” key/value pair to the “extra-volume-tags”

    spec:
      containers:
      - args:
        - controller
        - --endpoint=$(CSI_ENDPOINT)
        - --extra-volume-tags=deploy_id=DeploymentID,foo=bar
        - --k8s-tag-cluster-id=DeploymentOD
        - --logtostderr
        - --v=2

You could make these changes to the Helm chart too.