AWS Cost Explorer basics - Step-by-Step Execution

Process Flow - AWS Cost Explorer basics

User logs into AWS Console

↓

Open AWS Cost Explorer

↓

Select time range and filters

↓

View cost and usage data

↓

Analyze charts and reports

↓

Download or save reports if needed

↓

Exit

This flow shows how a user accesses AWS Cost Explorer, selects filters, views cost data, and optionally saves reports.

Execution Sample

AWS

1. Login to AWS Console
2. Open Cost Explorer
3. Choose last 7 days
4. Filter by service: EC2
5. View cost chart

This sequence shows how to view EC2 costs for the last 7 days using AWS Cost Explorer.

Process Table

Step	Action	Input/Selection	Result/Output
1	Login to AWS Console	User credentials	Access granted to AWS Management Console
2	Open Cost Explorer	Navigate via Billing dashboard	Cost Explorer interface loads
3	Select time range	Last 7 days	Cost data filtered to last 7 days
4	Apply filter	Service = EC2	Data shows only EC2 costs
5	View chart	Cost over time	Line chart displays daily EC2 costs
6	Download report	CSV format	Report file downloaded
7	Exit	Close Cost Explorer	Return to AWS Console home

💡 User finishes viewing and optionally downloads cost data, then exits Cost Explorer.

Status Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
Time Range	None	Last 7 days	Last 7 days	Last 7 days	Last 7 days
Service Filter	None	None	EC2	EC2	EC2
Displayed Data	None	All services last 7 days	EC2 last 7 days	EC2 last 7 days chart	EC2 last 7 days chart

Key Moments - 3 Insights

Why does the cost chart change after applying the service filter?

Because applying the filter narrows the data to only EC2 costs, as shown in execution_table step 4, the chart updates to reflect this filtered data.

What happens if no time range is selected before viewing data?

By default, Cost Explorer shows the last 7 days or a preset range, but explicitly selecting a time range (step 3) ensures you see the intended period's data.

Can you download reports for filtered data?

Yes, after filtering and viewing the data (step 5), you can download the report (step 6) which contains only the filtered cost information.

Visual Quiz - 3 Questions

Look at the execution_table, what filter is applied at step 4?

A Region = us-east-1

B Time range = Last 30 days

C Service = EC2

D No filter applied

💡 Hint

Check the 'Input/Selection' column at step 4 in the execution_table.

At which step does the cost chart display daily EC2 costs?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look at the 'Result/Output' column describing the chart display in the execution_table.

If the user changes the time range to last 30 days at step 3, how does the 'Displayed Data' variable change after step 3?

A It remains 'All services last 7 days'

B It changes to 'All services last 30 days'

C It changes to 'EC2 last 7 days'

D It becomes empty

💡 Hint

Refer to variable_tracker for 'Displayed Data' changes after step 3.

Concept Snapshot

AWS Cost Explorer basics:
- Login to AWS Console
- Open Cost Explorer from Billing
- Select time range (e.g., last 7 days)
- Apply filters (e.g., by service)
- View cost charts and reports
- Download reports if needed
- Exit when done

Full Transcript

AWS Cost Explorer lets you see your cloud costs visually. First, you log into the AWS Console. Then, you open Cost Explorer from the Billing dashboard. You select a time range, like the last 7 days, to focus your data. Next, you apply filters such as choosing a specific service like EC2. The cost charts update to show only the filtered data. You can download reports for offline use. Finally, you exit Cost Explorer when finished. This step-by-step process helps you understand and manage your AWS spending easily.

Practice

1. What is the main purpose of AWS Cost Explorer?

easy

A. To monitor network traffic

B. To create AWS virtual machines

C. To help you track and understand your AWS spending

D. To manage user permissions

Solution

1. Step 1: Understand AWS Cost Explorer's function

   AWS Cost Explorer is designed to show your cloud spending clearly and help manage costs.

2. Step 2: Compare options with this function

   Options A, B, and D describe other AWS services or features unrelated to cost tracking.

3. Final Answer:

   To help you track and understand your AWS spending -> Option C

4. Quick Check:

   Cost tracking = C [OK]

Hint: Cost Explorer is for spending, not resources or permissions [OK]

Common Mistakes:

• Confusing Cost Explorer with EC2 or IAM services
• Thinking it manages network or security settings

2. Which of the following is the correct way to start AWS Cost Explorer from the AWS Console?

easy

A. Go to Services > S3 > Cost Explorer

B. Go to Services > EC2 > Cost Explorer

C. Go to Services > IAM > Cost Explorer

D. Go to Services > Billing > Cost Explorer

Solution

1. Step 1: Identify where billing tools are located

   Cost Explorer is found under Billing in the AWS Console, not under EC2, IAM, or S3.

2. Step 2: Match the correct navigation path

   Only Go to Services > Billing > Cost Explorer correctly shows Services > Billing > Cost Explorer.

3. Final Answer:

   Go to Services > Billing > Cost Explorer -> Option D

4. Quick Check:

   Billing section = A [OK]

Hint: Cost Explorer is under Billing, not compute or storage [OK]

Common Mistakes:

• Looking for Cost Explorer under EC2 or S3
• Confusing IAM with billing tools

3. You use AWS Cost Explorer to view your monthly AWS costs grouped by service. If your report shows $100 for EC2 and $50 for S3, what does this mean?

medium

A. Your EC2 and S3 usage is free this month

B. You spent $100 on EC2 and $50 on S3 this month

C. You reserved EC2 instances worth $100 and S3 storage worth $50

D. You have $100 credit for EC2 and $50 credit for S3

Solution

1. Step 1: Understand grouping by service in Cost Explorer

   Grouping by service shows how much money you spent on each AWS service in the selected time.

2. Step 2: Interpret the amounts shown

   $100 for EC2 and $50 for S3 means those are your costs, not credits or reserved amounts.

3. Final Answer:

   You spent $100 on EC2 and $50 on S3 this month -> Option B

4. Quick Check:

   Costs shown = spending, not credits or free usage [OK]

Hint: Costs mean spending, not credits or reservations [OK]

Common Mistakes:

• Thinking amounts are credits or free usage
• Confusing cost with reserved capacity

4. You tried to filter your AWS Cost Explorer report by a tag, but no data appears. What is the most likely reason?

medium

A. The tag is not activated for cost allocation in AWS Billing settings

B. You have no AWS account

C. Cost Explorer does not support filtering by tags

D. You need to restart your AWS instance

Solution

1. Step 1: Understand tag filtering in Cost Explorer

   To filter by tags, the tags must be activated for cost allocation in Billing preferences.

2. Step 2: Identify why no data appears

   If the tag is not activated, Cost Explorer cannot use it to filter, so no data shows.

3. Final Answer:

   The tag is not activated for cost allocation in AWS Billing settings -> Option A

4. Quick Check:

   Tag activation needed for filtering = A [OK]

Hint: Activate tags in billing before filtering by them [OK]

Common Mistakes:

• Assuming Cost Explorer can't filter by tags
• Thinking AWS instance restart fixes this
• Believing no AWS account is the cause

5. You want to analyze your AWS costs for the last 3 months, grouped by linked accounts and filtered to only show costs for EC2 and S3. Which steps should you take in AWS Cost Explorer?

hard

A. Set the time range to last 3 months, group by linked accounts, and filter services to EC2 and S3

B. Set the time range to last 3 months, group by service, and filter accounts to EC2 and S3

C. Set the time range to last month, group by linked accounts, and filter services to all except EC2 and S3

D. Set the time range to last 3 months, group by tags, and filter services to EC2 only

Solution

1. Step 1: Choose correct time range and grouping

   Set the time range to last 3 months and group by linked accounts to see costs per account.

2. Step 2: Apply service filters correctly

   Filter services to only EC2 and S3 to focus on those costs.

3. Step 3: Verify options

   Set the time range to last 3 months, group by linked accounts, and filter services to EC2 and S3 matches all requirements. Other options have wrong grouping, filtering, or time range.

4. Final Answer:

   Set the time range to last 3 months, group by linked accounts, and filter services to EC2 and S3 -> Option A

5. Quick Check:

   Time + grouping + filter = B [OK]

Hint: Match time, grouping, and filters exactly for correct report [OK]

Common Mistakes:

• Mixing grouping by service vs linked accounts
• Filtering accounts instead of services
• Choosing wrong time range