Group costs with a project rule — Cost Explorer

Your goal

Create a category that groups costs by a project tag and inspect its rule.

Why this matters

Cost categories organize billing data using shared rules. You will create and rename a category value for a project tag. The exercise does not invent spending records or calculate actual savings.

Words you will use

A cost group combines related charges, such as one service. A filter narrows the view. A cost metric defines how amounts are calculated. Usage measures how much of a resource was consumed.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a project cost category

Create a cost category whose first rule groups Project=cloudarcade under Practice. Cost categories organize billing data. This emulator has no actual AWS bill or trustworthy production cost estimate.

2. Name the group in your own words

Choose a short label and update the category rule. The rule still matches the same project tag. Changing a grouping rule does not change the underlying price of any resource.

Practice label: This label is saved in the emulator. Use 1–80 characters. Suggested practice value: moonbase.

3. Inspect the grouping rule

Read the cost category and compare its value, tag key, and match condition. This lab checks a cost-analysis configuration rather than inventing spending data.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.