You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api-reference/api-services/aws.mdx
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ description: Follow these steps to deploy the Unstructured API service into your
6
6
<Warning>
7
7
This article describes how to create several interrelated resources in your AWS account.
8
8
Your AWS account will be charged on an ongoing basis for these resources, even if you are not actively using them.<br/><br/>
9
-
Manually stopping or terminating the associated Amazon EC2 instance alone will not reduce these ongoing charges.<br/><br/>
9
+
Manually stopping or terminating the associated Amazon EC2 instances alone will not reduce these ongoing charges.<br/><br/>
10
10
To stop accruing all related ongoing charges, you must delete all of the associated AWS resources.
11
11
To do this, see [Manage related AWS account costs](#manage-related-aws-account-costs).
12
12
</Warning>
@@ -330,18 +330,28 @@ If you need to access the Amazon EC2 instance that hosts the Unstructured API, d
330
330
331
331
## Manage related AWS account costs
332
332
333
-
After you run the CloudFormation stack, costs will begin accruing to your AWS account on an ongoing basis for related AWS resources.
334
-
These costs vary based on where these resource are located, which resources are covered by AWS Free Tier offerings, the extent to
333
+
After you run the CloudFormation stack that you created in Part II, charges will begin accruing to your AWS account on an ongoing basis for related AWS resources.
334
+
The amounts of these charges vary based on where these resource are located, which resources are covered by AWS Free Tier offerings, the extent to
335
335
which you customize these resources' settings, how much you use these resources, and other factors. Stopping or terminating
336
-
the related Amazon EC2 instance alone will not reduce these costs.
336
+
the related Amazon EC2 instances alone will not eliminate these ongoing charges.
337
337
338
-
To stop these costs from accruing, delete the CloudFormation stack. This stops and deletes all of the related AWS resources.
339
-
To delete the CloudFormation stack, do the following:
338
+
To stop these charges from accruing,
339
+
[delete the CloudFormation stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html)
340
+
that you created and ran in Part II. This stops and deletes all of the related AWS resources.
340
341
341
-
1. In the CloudFormation console, open the details page for the stack from Part II. If you do not see it, on the CloudFormation console's sidebar, click **Stacks**, and then click the name of your stack.
342
+
Before you delete the stack, note the following:
342
343
343
-
2. Click **Delete**.
344
+
- You should click the **Resources** tab on the stack's details page to be aware of the associated resources that will be deleted.
345
+
- You should note any resource dependencies, resources with deletion protection or termination protection enabled, or nested stacks
346
+
that might prevent stack deletion, and resolve these issues that could prevent stack deletion. To find these kinds of issues:
344
347
345
-
3. Follow the on-screen directions to finish deleting the stack.
348
+
- On the **Template** tab on the stack's details page, look for occurences of the `DependsOn` attribute, which are set to the name
349
+
of the resource dependency.
350
+
- On the **Template** tab on the stack's details page, look for occurences of the `DeletionPolicy` attribute set to `Retain` or the
351
+
`UpdateReplacePolicy` attribute set to `Retain`. The associated resources have deletion protection enabled.
352
+
- On the **Stack info** tab on the stack's details page, look for the **Termination protection** field. If it is set to **Activated**,
353
+
termination protection is enabled.
354
+
- On the **Resources** tab on the stack's details page, look for resources with their **Type** set to `AWS::CloudFormation::Stack`. These indicate nested stacks.
346
355
356
+
After you delete the stack, you should check your [AWS Billing and Cost Management dashboard](https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/billinginfo.html) to confirm that associated charges are no longer accruing.
0 commit comments