aws-amplify / aws-amplify/amplify-cli
S3 bucket does not get deleted in hosting.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### How did you install the Amplify CLI?
npm
### If applicable, what version of Node.js are you using?
_No response_
### Amplify CLI Version
8.3.0
### What operating system are you using?
Windows
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
### Amplify Categories
hosting
### Amplify Commands
delete
### Describe the bug
The hosting bucket created by amplify via `amplify add hosting` does not get deleted when removing the bucket using `amplify remove hosting` and then doing a push. Additionally, performed a `amplify delete` as well but the bucket persists.
### Expected behavior
Delete bucket when when removing the hosting and pushing it
### Reproduction steps
1. amplify add hosting
2. amplify push
3. amplify remove hosting
4. amplify push
5. amplify delete (optional)
### GraphQL schema(s)
```graphql
# Put schemas below this line
```
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
Contributor guide
Research direction
Start by reproducing the reported sequence with Amplify CLI 8.3.0: add hosting, push, remove hosting, push, and optionally delete. Trace the hosting removal and delete flow to see why the S3 bucket remains. Done means the bucket is removed after the documented commands and the reproduction no longer leaves it behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100