Skip to content

Commit 2305deb

Browse files
committed
revamp cost explorer
1 parent ab4efa9 commit 2305deb

File tree

1 file changed

+21
-24
lines changed
  • src/content/docs/aws/services

1 file changed

+21
-24
lines changed

src/content/docs/aws/services/cost-explorer.md renamed to src/content/docs/aws/services/ce.md

Lines changed: 21 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: "Cost Explorer"
3-
linkTitle: "Cost Explorer"
4-
description: >
5-
Get started with Cost Explorer on LocalStack
3+
description: Get started with Cost Explorer on LocalStack
64
tags: ["Ultimate"]
75
---
86

@@ -13,7 +11,7 @@ Cost Explorer offers options to filter and group data by dimensions such as serv
1311
With Cost Explorer, you can forecast costs, track budget progress, and set up alerts to receive notifications when spending exceeds predefined thresholds.
1412

1513
LocalStack allows you to use the Cost Explorer APIs in your local environment to create and manage cost category definition, cost anomaly monitors & subscriptions.
16-
The supported APIs are available on our [API coverage page]({{< ref "coverage_ce" >}}), which provides information on the extent of Cost Explorer's integration with LocalStack.
14+
The supported APIs are available on our [API coverage page](), which provides information on the extent of Cost Explorer's integration with LocalStack.
1715

1816
## Getting started
1917

@@ -27,10 +25,10 @@ We will demonstrate how to mock the Cost Explorer APIs with the AWS CLI.
2725
You can create a Cost Category definition using the [`CreateCostCategoryDefinition`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CreateCostCategoryDefinition.html)) API.
2826
The following example creates a Cost Category definition using an empty rule condition of type "REGULAR":
2927

30-
{{< command >}}
31-
$ awslocal ce create-cost-category-definition --name test \
28+
```bash
29+
awslocal ce create-cost-category-definition --name test \
3230
--rule-version "CostCategoryExpression.v1" --rules '[{"Value": "test", "Rule": {}, "Type": "REGULAR"}]'
33-
{{< /command >}}
31+
```
3432

3533
The following output would be retrieved:
3634

@@ -43,10 +41,10 @@ The following output would be retrieved:
4341
You can describe the Cost Category definition using the [`DescribeCostCategoryDefinition`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DescribeCostCategoryDefinition.html) API.
4442
Run the following command:
4543

46-
{{< command >}}
47-
$ awslocal ce describe-cost-category-definition \
44+
```bash
45+
awslocal ce describe-cost-category-definition \
4846
--cost-category-arn arn:aws:ce::000000000000:costcategory/test
49-
{{< /command >}}
47+
```
5048

5149
The following output would be retrieved:
5250

@@ -72,16 +70,16 @@ The following output would be retrieved:
7270
You can add an alert subscription to a cost anomaly detection monitor to define subscribers using the [`CreateAnomalySubscription`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CreateAnomalySubscription.html) API.
7371
The following example creates a cost anomaly subscription:
7472

75-
{{< command >}}
76-
$ awslocal ce create-anomaly-subscription --anomaly-subscription '{
73+
```bash
74+
awslocal ce create-anomaly-subscription --anomaly-subscription '{
7775
"AccountId": "12345",
7876
"SubscriptionName": "sub1",
7977
"Frequency": "DAILY",
8078
"MonitorArnList": [],
8179
"Subscribers": [],
8280
"Threshold": 111
8381
}'
84-
{{< /command >}}
82+
```
8583

8684
The following output would be retrieved:
8785

@@ -94,9 +92,9 @@ The following output would be retrieved:
9492
You can retrieve the cost anomaly subscriptions using the [`GetAnomalySubscriptions`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_GetAnomalySubscriptions.html) API.
9593
Run the following command:
9694

97-
{{< command >}}
98-
$ awslocal ce get-anomaly-subscriptions
99-
{{< /command >}}
95+
```bash
96+
awslocal ce get-anomaly-subscriptions
97+
```
10098

10199
The following output would be retrieved:
102100

@@ -121,12 +119,12 @@ The following output would be retrieved:
121119
You can create a new cost anomaly detection subscription with the requested type and monitor specification using the [`CreateAnomalyMonitor`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CreateAnomalyMonitor.html) API.
122120
The following example creates a cost anomaly monitor:
123121

124-
{{< command >}}
125-
$ awslocal ce create-anomaly-monitor --anomaly-monitor '{
122+
```bash
123+
awslocal ce create-anomaly-monitor --anomaly-monitor '{
126124
"MonitorName": "mon5463",
127125
"MonitorType": "DIMENSIONAL"
128126
}'
129-
{{< /command >}}
127+
```
130128

131129
The following output would be retrieved:
132130

@@ -139,9 +137,9 @@ The following output would be retrieved:
139137
You can retrieve the cost anomaly monitors using the [`GetAnomalyMonitors`](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_GetAnomalyMonitors.html) API.
140138
Run the following command:
141139

142-
{{< command >}}
143-
$ awslocal ce get-anomaly-monitors
144-
{{< /command >}}
140+
```bash
141+
awslocal ce get-anomaly-monitors
142+
```
145143

146144
The following output would be retrieved:
147145

@@ -162,8 +160,7 @@ The following output would be retrieved:
162160
The LocalStack Web Application provides a Resource Browser for managing cost category definitions for the Cost Explorer service.
163161
You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the Resources section, and then clicking on **Cost Explorer** under the **Cloud Financial Management** section.
164162

165-
<img src="cost-explorer-resource-browser.png" alt="Cost Explorer Resource Browser" title="Cost Explorer Resource Browser" width="900" />
166-
<br><br>
163+
![Cost Explorer Resource Browser](/images/aws/cost-explorer-resource-browser.png)
167164

168165
The Resource Browser allows you to perform the following actions:
169166

0 commit comments

Comments
 (0)