aws-amplify / aws-amplify/amplify-cli

When a build fails or an app is delete, s3 buckets must be manually deleted

Open
#558 2 comments 3 reactions 0 assignees View on GitHub
feature-request p4 pending-review storage
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

Orignal Issue from: https://forums.aws.amazon.com/thread.jspa?threadID=294766&tstart=0

When added a bucket via amplify storage add and then the `amplify push` fails to complete, the S3 bucket won't be deleted. This means you have to manually delete the s3 bucket to re-attempt the `amplify push`.

Suggested fix: There should be some logic to detect if the bucket was newly created and delete the bucket on CloudFormation rollback.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.