Deleting back-end environment just deleted all our S3 data?!

[jamescrowley]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

d3dw5sp1sablwh

Region

eu-west-1

Amplify Console feature

Backend builds

Describe the bug

Deleting our back-end deleted the storage S3 bucket (along with all its contents), despite the fact the cloudformation retention policy was set to retain.

		"DeletionPolicy" : "Retain",

(I double checked before triggering the delete from amplify).

We tested deleting the dev environment, but due to #2369 we had to delete manually from cloud formation, which worked as expected and retained the S3 bucket and it's data.

When deleting the production environment, the CloudFormation log clearly shows it being retained as expected

and yet somehow subsequently Amplify deletes it later in the process when deleting from the console?

Expected behavior

You should not delete data in S3 storage buckets without warning! What am I missing here? This seems a completely insane default behaviour without some kind of UI warning or confirmation or option.

Reproduction steps

1. Create back-end environment configured with storage
2. Store data in storage
3. Delete back-end environment

Build Settings

No response

Additional information

No response

[github-actions]

Hi 👋, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

[ghost]

Hi @jamescrowley 👋🏽 thank you for raising this issue. We are treating this as a priority and are currently investigating this behavior. We will provide an update as soon as possible.

[ghost]

@jamescrowley This is default behavior when deleting backend environments. Buckets are generated with the "DeletionPolicy" : "Retain" policy so that they aren't deleted when running CLI commands like amplify remove. However, deleting your backend will remove all resources associated with that project.

We appreciate your feedback and will update our UI to include a clear warning to emphasize this behavior.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.