Docs for what is not deleted when running Amplify Delete

[wizage]

Is your feature request related to a problem? Please describe. Define what is not deleted from the project when you run amplify delete

Describe the solution you'd like Lay out in the docs which resources will need to be cleaned up by hand.

Additional context Add any other context or screenshots about the feature request here.

[kylekirkby]

Hey @wizage,

Any update on this one? I'm about to delete a test project but I'm now questioning whether there will be a tonne of resources laying around, still?

Cheers!

Kyle

[wizage]

Hey @kylekirkby

We are forgoing this as we are working with the Amplify team to fix the clean up so soon everything will just be deleted on Amplify Delete 👍

The biggest things not cleaned up for your info:

VOD Projects:

• S3 Buckets & Objects for input and output bucket
• Secrets found in Secrets Manager (if using CloudFront signed urls)

Livestream (non-ivs):

• Verify MediaLive is shutdown
• Verify MediaStore is empty and deleted

IVS:

• All will be deleted!

[kylekirkby]

Hey @wizage,

Thanks for the info! I take it you're going to add this to the WIKI GitHub doesn't actually support creating a pull request for the repo wiki. Maybe we should look at moving the docs into a separate repo or a subfolder? We could build the docs with RTD or something? That way it will scale going forward :)

Cheers!

Kyle

[smp]

@kylekirkby we just changed with permissions on the wiki to allow anyone to edit. Feel free to make changes.

If you have suggestions on how to auto-build the wiki for /docs folder in the main repo, we're all ears. The default implementation of github wiki is a bit lacking...