Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added info about stack deletion #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/partner_editable/faq_troubleshooting.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,3 +14,7 @@ For additional information, see https://docs.aws.amazon.com/AWSCloudFormation/la
*Q.* I encountered a size limitation error when I deployed the AWS CloudFormation templates.

*A.* Launch the Quick Start templates from the links in this guide or from another S3 bucket. If you deploy the templates from a local copy on your computer or from a location other than an S3 bucket, you might encounter template size limitations. For more information about AWS CloudFormation quotas, see the http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html[AWS documentation^].

*Q.* When deleting the stack, I encounter an error that `Etleap-Deployment` deployment stack failed to delete

*A.* This happens because of EMR security groups, and is a known limitation of CloudFormation. To get around this, you need to manually delete the embedded `Etleap-Deployment` stack again, and *retain* the `Etleap VPC` resource. Once the stack is deleted, you can delete the VPC from the AWS Console. You can also delete the top-level stack, and retain the `Etleap-Deployment` stack, as it has already been deleted.