Cost management and tagging turn a mysterious monthly bill into a transparent, controllable system. For someone studying for the PAS-C01 exam, understanding these concepts is the difference between a business running an affordable, predictable SAP platform and one that gets a shocking, unaffordable invoice. Mastering them shows you can run SAP like a disciplined business, not a chaotic experiment.
Jump to a section
A simple way to picture Cost Management and Tagging for SAP on AWS
Your credit card statement at the end of the month is a blunt, confusing lump of numbers. It tells you the total you spent, but it doesn't tell you if that big charge was for car repairs, a birthday present, or that electric scooter you bought on a whim. Without this breakdown, you cannot know if you are spending too much on takeaway coffee or if your electricity bill has doubled. This is exactly the problem that cost management and tagging solve for SAP systems running on AWS.
Tagging is like giving every single purchase its own sticky note. You write the project name, the department, and the environment (like 'Production' or 'Test') on each note. When the monthly bill arrives, you can instantly sort everything. You can see that the 'Marketing' team spent $500 on their test system this month, while the 'Finance' team's production system cost $2,000. Reserved Instances are like buying a year-long bus pass instead of paying for every single ride. You pay a large chunk upfront, but your daily cost plummets. AWS Cost Explorer is your budgeting app. It shows you trends, predicts next month's bill based on your tagged history, and helps you spot where you could switch from single tickets to a bus pass. Without these tools, your AWS bill is just a scary number. With them, you control it like a personal finance guru.
Let's start with the problem. You are running an SAP system on AWS. SAP is the heart of your company's operations—handling everything from finance to supply chain. It is powerful, but it is also hungry for computing resources. Every hour, your virtual servers (Amazon EC2 instances), your storage (Amazon EBS volumes), and your network traffic all cost money. At the end of the month, AWS sends you a bill. Without any organisation, this bill is just a long list of line items: 'EC2 Instance m5.xlarge, 720 hours, $144' and 'EBS gp3, 500 GB, $30'. You cannot tell which costs belong to your SAP test environment versus your production environment. You cannot tell which department is driving the costs.
This is where tagging enters the scene. A tag is a simple label that you attach to every AWS resource. It is made of two parts: a key and a value. For example, you create a tag with the key 'Environment' and the value 'Production'. You attach that tag to every EC2 instance, every storage volume, and every database that belongs to your production SAP system. You create another tag with the key 'Department' and the value 'Finance'. Now, when you get your bill, you can filter it by these tags. The bill magically reorganises itself: 'Production Environment total: $10,000. Finance Department total: $12,000.' Tags turn chaos into clarity. For the PAS-C01 exam, you must know that tagging is the foundation of all cost management. Without consistent tagging, you cannot analyse costs or optimise them.
Now, let's talk about why tagging alone is not enough. Once you can see your costs, you notice patterns. For instance, your SAP production system runs 24 hours a day, 7 days a week. But your SAP test and development systems only need to run during business hours. Yet, if you leave them running all night and all weekend, you are paying for wasted compute power. This is where a cost optimisation strategy called Rightsizing comes in. Rightsizing means matching your instance type to your actual workload. If your SAP system is only using 20% of its CPU capacity, you can switch to a smaller, cheaper instance. AWS provides tools like AWS Compute Optimizer that analyse your usage and recommend better sizes.
Another powerful strategy is Reserved Instances (RIs). Think of an RI as a commitment. You agree to use a specific instance type in a specific region for one or three years. In return, AWS gives you a big discount—often 40% to 60% off the normal hourly price. This makes sense for your SAP production system because you know it will run constantly. However, it makes no sense for a test system that you might decommission next month. The exam will test whether you know when to use RIs versus On-Demand (pay-as-you-go) instances.
AWS also offers Savings Plans, which are similar to RIs but more flexible. A Savings Plan is a commitment to spend a certain amount per hour for one or three years. It covers any EC2 instance, not just a specific type. For SAP systems that may need different instance types over time, Savings Plans are often a better choice than RIs.
Finally, AWS Cost Explorer is the tool you use to see, analyse, and forecast your costs. It uses your tags to break down spending. You can create custom reports, set budgets, and receive alerts when you are about to exceed your budget. For example, you can set a budget of $5,000 for your SAP development environment. If costs hit $4,500, you get an email warning you to shut down unused resources.
In summary, the workflow is simple: tag your resources consistently, use Cost Explorer to view costs by tag, identify waste (like idle instances), right-size those instances, and apply RIs or Savings Plans to the stable, long-running workloads. This is the core of Domain 4.3.
Define a Tagging Policy
Before you tag anything, decide on a set of tag keys that matter for cost allocation. Common keys for SAP are 'Environment', 'CostCenter', 'Application', and 'Owner'. Agree with your team that all resources for the SAP system must have these tags. This step is crucial because inconsistent tagging leads to incomplete cost data in Cost Explorer.
Apply Tags to All SAP Resources
Go into the AWS Management Console and apply the agreed tags to every EC2 instance, EBS volume, Elastic Load Balancer, and database used by SAP. For existing resources, you can apply tags manually or use AWS Resource Groups and Tag Editor to do it in bulk. New resources should be tagged automatically using AWS CloudFormation or Terraform scripts.
Activate Cost Allocation Tags
Navigate to the AWS Billing and Cost Management console. Under 'Cost Allocation Tags', find the tag keys you defined (e.g., 'Environment') and activate them. Without this step, your tags will exist on resources but will not appear as filters in Cost Explorer reports. This is a common oversight that causes beginners to think tagging 'does not work'.
Analyse Costs with AWS Cost Explorer
Open AWS Cost Explorer and set the 'Group by' dimension to your activated cost allocation tag, such as 'Environment'. You will now see a bar chart showing cost per environment. Identify which environment (e.g., Test) is consuming an unexpectedly high percentage. This gives you a target for cost reduction.
Identify Waste and Apply Savings Strategies
Based on your Cost Explorer analysis, pinpoint specific instances that run 24/7 but only need to run 8 hours a day. Deploy AWS Instance Scheduler to auto-stop them outside business hours. Also use AWS Compute Optimizer to find oversized instances and right-size them. For steady-state production instances, purchase Reserved Instances or a Savings Plan.
Set Budgets and Alerts
Create a budget in AWS Budgets for each environment. For example, set a monthly cost budget of $5,000 for the Test environment. Configure an alert at 80% ($4,000) and 100% ($5,000) that sends an email to the SAP team. This ensures you are notified before costs run away again.
Let's walk through a realistic day in the life of a cloud architect managing an SAP system for a mid-sized retail company called 'ShopRight'. ShopRight uses SAP for inventory, sales, and accounting. They run three SAP environments on AWS: Production (always on), Test (used during the day), and Development (used a few hours a week). The company's CFO has just received the monthly AWS bill of $50,000 and is not happy. The CFO demands: 'Break down exactly why we spent $50,000 and find a way to cut it by 20%.'
You, as the cloud architect, start using AWS Cost Explorer. You have already implemented tagging using a standard policy. Each resource has tags for: Environment (Production, Test, Development), Cost Center (Finance, IT, Sales), and Owner (the team responsible). You open Cost Explorer and group costs by the 'Environment' tag. Immediately, you see that Production costs $35,000, Test costs $10,000, and Development costs $5,000. The $35,000 for Production is expected. But $10,000 for Test seems high for a system that only runs 8 hours a day.
You dig deeper. You filter Cost Explorer by 'Environment: Test' and then by 'Service: EC2-Instances'. You see that the Test environment has ten m5.xlarge instances running 24/7. That is the waste. They should only run during business hours (8 AM to 6 PM). You also notice that four of those ten instances are only using about 10% of their CPU. They are oversized.
Here is your step-by-step action plan:
First, you set up AWS Instance Scheduler. This is a solution that automatically starts and stops EC2 instances based on a schedule. You configure it so that all Test environment instances start at 8 AM and stop at 6 PM, Monday to Friday. You estimate this alone cuts the Test environment cost by more than half—from $10,000 to about $4,000.
Second, you use AWS Compute Optimizer. It recommends that the four under-utilised instances be changed from m5.xlarge (4 vCPUs, 16 GB RAM) to m5.large (2 vCPUs, 8 GB RAM). This saves another $1,000 per month.
Third, you review the Production environment. It must run 24/7, so you cannot schedule it to stop. Instead, you look at the running costs. You see that Production has been running on On-Demand instances, paying full price. You calculate that switching to a three-year, all-upfront Reserved Instance would save 60%. The $35,000 monthly bill could drop to $14,000. You run the numbers and present this to your manager.
Fourth, you create a budget in AWS Budgets for the Test environment: a monthly limit of $5,000. If the cost goes over $4,500, you get an alert.
By the end of the month, you have reduced the total bill from $50,000 to $28,000. The CFO is thrilled. The exam tests your ability to think through this exact kind of scenario: identify waste using tags, apply scheduling, right-size, and then apply RIs or Savings Plans to stable workloads.
The PAS-C01 exam will test your understanding of cost management and tagging in several specific ways. First, expect scenario-based questions. They describe a company running SAP on AWS with a high bill. The question asks: 'What is the MOST cost-effective solution to reduce costs without impacting availability?' Your job is to pick the right combination of tools and strategies.
The exam loves to test the difference between Reserved Instances (RIs) and Savings Plans. A common trap question is: 'A company has a steady-state SAP production workload that uses multiple EC2 instance types over the year. Should they use RIs or Savings Plans?' The correct answer is Savings Plans, because Savings Plans are instance-family flexible, while RIs lock you into a specific instance type. If the company uses only one instance type year-round, RIs are preferred because they offer a slightly higher discount.
Another trap is around the concept of 'Resource Tagging' versus 'Cost Allocation Tags'. Many beginners think they are the same. But the exam tests that you understand cost allocation tags are the specific tags that AWS activates in the billing console to appear in Cost Explorer reports. You must activate them before they appear. You also need to know that tags are not retroactive—they only apply to new usage after they are applied.
The exam also tests 'Elasticsearch' indirectly. AWS Cost Explorer uses a data source called AWS Cost and Usage Report (CUR), which is a detailed CSV file of all your account usage. You must know that CUR can be integrated with services like Amazon Athena and Amazon QuickSight for custom analytics, but the default tool is Cost Explorer.
Here are the exact concepts you need to memorise:
Cost Allocation Tags: must be activated in the Billing console to appear in reports.
Reserved Instances: best for steady-state, single instance type workloads. 1-year or 3-year terms. Partial upfront gives a lower discount than all upfront.
Savings Plans: compute flexible, best for changing instance types. Also 1-year or 3-year terms.
AWS Instance Scheduler: a solution from AWS that stops/starts instances on a schedule to save cost.
AWS Compute Optimizer: recommends rightsizing based on CloudWatch metrics.
AWS Budgets: set cost limits and receive alerts.
The 'No Upfront' vs 'Partial Upfront' vs 'All Upfront' distinction for RIs: all upfront gives the biggest discount.
Be ready for a question that shows a graph in Cost Explorer. They will ask: 'Based on the graph, which tag shows the highest cost?' You must read the axis labels and the legend quickly. Also expect a question where a company has unused RIs that they want to sell back. The answer is the AWS Reserved Instance Marketplace.
Finally, the exam will not ask you to write tagging policies, but it will ask you to diagnose why a cost analysis is failing. The most common cause of failure is that tags are not activated in the billing console, or that tags have inconsistent values (e.g., 'Prod' on some resources and 'Production' on others). Remember: tag keys and values are case-sensitive and must match exactly for filtering to work.
Cost allocation tags must be activated in the Billing console before they appear in Cost Explorer reports.
Reserved Instances offer the biggest discount for steady-state, single instance type workloads on a 1-year or 3-year commitment.
Savings Plans provide instance-family flexibility and are better for SAP environments that use multiple instance types over time.
AWS Instance Scheduler can automatically start and stop non-production SAP instances to reduce costs by up to 70%.
AWS Compute Optimizer analyses CPU and memory utilisation to recommend rightsizing EC2 instances.
AWS Budgets allow you to set cost thresholds and receive alerts before costs exceed your limit.
Tags are case-sensitive and must have consistent key-value conventions across your entire AWS account for accurate cost grouping.
You can sell unused Reserved Instances on the AWS Reserved Instance Marketplace to recover costs.
These come up on the exam all the time. Here's how to tell them apart.
Reserved Instance (RI)
Locked to a specific instance type (e.g., m5.xlarge) in a specific region.
Offers slightly higher discounts (up to 72%) for steady-state workloads.
Cannot change instance type without incurring a modification fee or losing the discount.
Savings Plan (SP)
Flexible across instance types within a family (EC2 SP) or all compute (Compute SP).
Slightly lower maximum discounts (up to 66%) but more adaptable.
Automatically applies to any instance that meets the commitment, no changes needed.
On-Demand Instances
Pay per hour with no upfront commitment.
Highest cost per hour, ideal for short-term or unpredictable workloads.
Can be stopped or terminated at any time without penalty.
Reserved Instances
Require a 1-year or 3-year commitment.
Up to 72% cheaper than On-Demand for steady workloads.
Early termination incurs a fee; best for long-running production systems.
Resource Tags
Applied to individual AWS resources for general organisation.
Visible only in the resource console (e.g., EC2 console).
Do not appear in billing reports by default.
Cost Allocation Tags
Activated from resource tags in the Billing console.
Visible in AWS Cost Explorer and Cost and Usage Reports.
Specifically used for grouping and filtering costs in billing analysis.
Mistake
Tags are automatically visible in Cost Explorer the moment you apply them to a resource
Correct
Tags must be activated as cost allocation tags in the AWS Billing and Cost Management console before they appear in Cost Explorer reports.
Because AWS separates resource tags from billing tags for security and performance reasons, so activation is a deliberate step that beginners often skip.
Mistake
Reserved Instances and Savings Plans are the same thing, just with different names
Correct
Reserved Instances are locked to a specific instance type in a specific region, while Savings Plans are flexible across instance types within a family (EC2 Instance Savings Plans) or across all compute services (Compute Savings Plans).
Because the terms sound interchangeable and AWS documentation can be complex, leading beginners to think they are identical.
Mistake
Using tags means I cannot see my costs without tags
Correct
Costs are always visible in Cost Explorer without tags; tags just let you filter and group costs in a meaningful way.
Because the emphasis on tagging makes beginners think it is mandatory for cost visibility, when in fact it is optional but strongly recommended for analysis.
Mistake
I can only use AWS Cost Explorer for cost analysis; no other AWS service is needed
Correct
AWS Cost Explorer is great for high-level analysis, but for deep custom reports, you need the AWS Cost and Usage Report (CUR) combined with services like Amazon Athena or Amazon QuickSight.
Because Cost Explorer is the most visible tool, so beginners assume it is the only option, missing the fact that CUR offers far more granularity.
Mistake
Stopping an EC2 instance saves money by automatically removing the attached EBS storage costs
Correct
Stopping an instance stops compute charges, but you still pay for the attached EBS storage volumes and any Elastic IP addresses not associated with a running instance.
Because beginners think 'stopped' means 'no cost at all', but storage persists and still incurs charges.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
You need to have tagged all your SAP resources with a tag like 'CostCenter' or 'Department'. Then activate that tag as a cost allocation tag in the Billing console. In Cost Explorer, group your costs by that tag to see the department breakdown.
A Reserved Instance (RI) commits you to a specific EC2 instance type in a specific region for 1 or 3 years, giving a discount of up to 72%. A Savings Plan commits you to a spend amount per hour, covering any EC2 instance or even all compute services, with discounts up to 66%. Use RIs for your stable, predictable SAP production. Use Savings Plans if you might change instance types.
No, in most cases SAP production must run 24/7 to support business operations. Stopping it would cause downtime, lost transactions, and potentially unhappy customers. Use Reserved Instances or Savings Plans to reduce the hourly cost instead.
Most likely you have not activated them as cost allocation tags. Go to the Billing and Cost Management console, find 'Cost Allocation Tags', locate your tag keys, and click 'Activate'. Also remember that activation can take up to 24 hours to take effect.
Use AWS Instance Scheduler. It is a solution available in the AWS Solutions Library. You define a schedule (e.g., start at 8 AM, stop at 6 PM, Monday to Friday) and tag your test instances with a specific tag. The scheduler automatically turns them on and off, saving you up to 70% on compute costs.
All upfront gives you the largest discount because you pay the entire amount at the start. Partial upfront gives a smaller discount, and no upfront gives the smallest. If you have the cash flow, choose all upfront for maximum savings. If you prefer to conserve cash, choose partial upfront or no upfront.
You've finished Cost Management and Tagging for SAP on AWS. Continue through the PAS-C01 study guide to build a complete picture of the exam.
Done with this chapter?