aws-amplify / aws-amplify/amplify-hosting

On deletion of Amplify Hosting, not all services are deleted and there is no reference

Open
#2,876 0 comments 0 reactions 0 assignees View on GitHub
bug UX
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

d1mptt8hqo6wak

### Region

us-east-1

### Amplify Hosting feature

Backend builds

### Describe the bug

**Issue 1**

OBSERVATION:
I don't know what services Amplify deploys and where they reside.

EXPECTED BEHAVIOUR
Under Amplify Application in https://us-east-1.console.aws.amazon.com/amplify/home I would like to see a section that shows me all the AWS services that have been created for this application, and I want to be able to click on them to get to them on the AWS Web console.

**Issue 2**

When deleting the Amplify application some services are not deleted such as:
- Lambda functions that are created, without any reference to the amplify app
- Cognito pool that is created, without any reference to the amplify app
- There are IAM roles created which thankfully have the name of the amplify app in them

Without an overview of which services Amplify has deployed where, and without AWS removing all services it created, the risk is too high for me to use Amplify in production. I'm stranded with services that I don't know if they're still used or not, and if I can delete them. This leaves me with a mess in my AWS account.

I'm not the only one, when I was talking to a friend recently he told me that he gave up on Amplify for this reason, and has now created a WebSocket connection with Lambda functions. It was too intransparent for him, and it's also too intransparent for me at the moment.

![Screenshot 2022-07-20 at 11 12 07 PM](https://user-images.githubusercontent.com/6489758/180019472-65b115b9-37e7-4523-a936-5a0e722dd51d.png)

![Screenshot 2022-07-20 at 11 18 29 PM](https://user-images.githubusercontent.com/6489758/180020044-0952a0b6-b745-4922-b852-deca29da0bcc.png)

### Expected behavior

See above.
- I want to know which services are associated with my Amplify application
- I want that when I delete the application all the services are deleted, not only part of them
- I want that each of the services has the application name within the name of the service or another way of reference.

### Reproduction steps

1. Create an Amplify App
2. Delete the Amplify App
3. Look at the Lambda Service
4. Look at the Cognito Service

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported lifecycle with the Amplify Application console in us-east-1: create an app, delete it, then inspect Lambda and Cognito, including related IAM roles. Review how the application tracks and removes AWS services. Done means associated services are discoverable, references are clear, and deletion behavior is documented or complete.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.