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
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,13 @@ title: Unstructured API on AWS
3
3
description: Follow these steps to deploy the Unstructured API service into your AWS account.
4
4
---
5
5
6
-
<Warning>This article describes how to create several interrelated resources in your AWS account. Your AWS account will be charged on an ongoing basis for these resources, even if you are not actively using them. To stop accruing charges you must delete all of these resources. To do this, see [Manage related AWS account costs](#manage-related-aws-account-costs).</Warning>
6
+
<Warning>
7
+
This article describes how to create several interrelated resources in your AWS account.
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/>
10
+
To stop accruing all related ongoing charges, you must delete all of the associated AWS resources.
11
+
To do this, see [Manage related AWS account costs](#manage-related-aws-account-costs).
12
+
</Warning>
7
13
8
14
_Estimated time to complete: 30 minutes_
9
15
@@ -326,10 +332,10 @@ If you need to access the Amazon EC2 instance that hosts the Unstructured API, d
326
332
327
333
After you run the CloudFormation stack, costs will begin accruing to your AWS account on an ongoing basis for related AWS resources.
328
334
These costs vary based on where these resource are located, which resources are covered by AWS Free Tier offerings, the extent to
329
-
which you customize these resources' settings, how much you use these resources, and other factors. Even if you stop or terminate
330
-
the related EC2 instance and delete the related application load balancer, costs might continue to accrue for other related AWS sources.
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.
331
337
332
-
To stop these costs from accruing, you can delete the CloudFormation stack. This stops and deletes all of the related AWS resources.
338
+
To stop these costs from accruing, delete the CloudFormation stack. This stops and deletes all of the related AWS resources.
333
339
To delete the CloudFormation stack, do the following:
334
340
335
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.
Copy file name to clipboardExpand all lines: api-reference/api-services/azure.mdx
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,12 @@ title: Unstructured API on Azure
4
4
5
5
Follow these steps to deploy the Unstructured API service into your Azure account.
6
6
7
-
<Warning>This deployment will create a virtual machine with its own instance of the Unstructured API. To avoid unexpected charges, be sure to shut down the virtual machine when not in use.</Warning>
7
+
<Warning>
8
+
This article describes how to create several interrelated resources in your Azure account.
9
+
Your Azure account will be charged on an ongoing basis for these resources, even if you are not actively using them.<br/><br/>
10
+
Manually shutting down the associated Azure virtual machine when you are not using it can help reduce—but not fully eliminate—these ongoing charges.<br/><br/>
11
+
To stop accruing all related ongoing charges, you must delete all of the associated Azure resources.
0 commit comments