aws-amplify / aws-amplify/amplify-hosting

Deleting App process deleted the backend environment of another app

Open
#2,891 8 comments 0 reactions 0 assignees View on GitHub
bug console
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

ddhhh5znoq37b & d3sy22uqr5mvv6

### Region

eu-central-1

### Amplify Hosting feature

_No response_

### Describe the bug

While deleting APP2 (which did only host the frontend & relayed on the backend of APP1) the process failed and deleted the production environment of APP1.

The backend production environment of APP1 is now deleted and listed under APP2 in the GUI.

### Expected behavior

This should never happen. Not sure even why this has happened. Only the app flagged to be deleted should have been deleted.

### Reproduction steps

1. Create APP1 with backend environment
2. Create APP2 (only frontend hosting relaying on APP1s backend)
3. Build & deploy app2
4. Delete APP2

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the reported reproduction in the Amplify Hosting GUI using APP1 and APP2 in eu-central-1, and review the deletion behavior described in FAQ.md. Done means deleting the frontend-only APP2 does not delete or reassign APP1's production backend environment; the issue provides no source files or tests to target.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
backend, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.