This chapter covers AWS License Manager, a service that helps you manage software licenses from vendors like Microsoft, Oracle, and SAP across AWS and on-premises environments. For the SOA-C02 exam, License Manager appears in the Cost domain (Objective 6.1) and typically accounts for 2-4% of questions. Understanding how to create license configurations, track usage, and enforce limits is critical for cost optimization and compliance scenarios. You will encounter questions about license rules, inventory tracking, and integration with Systems Manager.
Jump to a section
AWS License Manager works like a corporate library checkout system for software licenses. Imagine your company has purchased 100 licenses for a specialized engineering software, each represented by a physical token. The library (License Manager) maintains a central registry of all tokens and their allowed usage terms—like how many concurrent checkouts are permitted, which departments can borrow them, and for how long. When an engineer (EC2 instance) needs to use the software, their computer sends a request to the library's checkout counter (License Manager API). The librarian checks the registry: if there are available tokens and the request complies with the terms (e.g., the engineer is from the authorized department, the software version matches), the librarian hands over a token and records the checkout in the log. The engineer can then run the software locally. When the engineer returns the token (instance termination or license release), the librarian updates the registry, making the token available for others. The library also integrates with the company's procurement system (AWS Marketplace) to automatically add new tokens when purchased. If an engineer tries to borrow a token when none are available, the librarian rejects the request, and the software fails to launch—preventing license violations. This system ensures the company never exceeds its 100-token limit, avoids audit penalties, and provides a clear audit trail of who used which license and when.
What is AWS License Manager and Why Does It Exist?
AWS License Manager is a service that enables you to manage software licenses from vendors that use bring-your-own-license (BYOL) models, such as Microsoft Windows Server, SQL Server, Oracle Database, and SAP. Many organizations have existing enterprise agreements with volume licensing, and moving to the cloud can create compliance risks if license usage exceeds purchased entitlements. License Manager provides a centralized way to define license rules (e.g., maximum number of cores, allowed instance families, expiration dates) and enforce them across EC2 instances, RDS databases, and on-premises servers. It integrates with AWS Systems Manager to discover resources and track license consumption.
How License Manager Works Internally
License Manager operates through two main components: license configurations and license endpoints. A license configuration is a set of rules that define the terms of your license agreement. You create one for each license type you want to manage. The configuration includes: - Name and description - License type: Choose from a predefined list (e.g., Microsoft Windows Server, Oracle Database) or create a custom type. - License counting rule: How license consumption is measured—per core, per socket, per instance, or per user. For example, SQL Server Enterprise Edition is often licensed per core. - Allowed instance families: Restrict usage to specific EC2 instance families (e.g., only m5 and r5, not t2). - Allowed tenancy: Dedicated or default. - Maximum number of licenses: The total number of licenses you have purchased. - Expiration date: When the license agreement ends. - License tags: Metadata for reporting.
Once you create a license configuration, you associate it with AWS resources (EC2 instances, RDS DB instances) or on-premises servers via Systems Manager. License Manager then tracks consumption in near real-time. It uses the AWS Systems Manager Agent (SSM Agent) to collect inventory data from managed instances, such as operating system, processor type, number of cores, and installed software. For EC2 instances, License Manager can also use EC2 metadata to determine instance type and tenancy.
Key Components, Values, and Defaults
License Configuration: The blueprint for license tracking. You can create up to 1000 license configurations per AWS account.
License Endpoint: A regional resource that represents your license inventory. Each license configuration has a unique ARN.
License Consumption: Measured based on the counting rule. For example, if the rule is "per core" and you associate an m5.xlarge instance (4 cores), it consumes 4 licenses.
License Validity: You can set an expiration date. If a license configuration expires, resources associated with it are marked as non-compliant.
License Rules: Include allowed instance families, allowed tenancy, and maximum license count. If a rule is violated, the resource is flagged as non-compliant.
Inventory: License Manager collects inventory from Systems Manager. You must have SSM Agent installed and the instance must be managed by Systems Manager for on-premises servers.
Reporting: License Manager provides a dashboard showing license consumption, compliance status, and usage trends. You can export reports to S3 or CloudWatch.
Integration with AWS Organizations: You can use License Manager across multiple accounts in an organization by enabling trusted access.
Configuration and Verification Commands
To create a license configuration via AWS CLI:
aws license-manager create-license-configuration \
--name "MyWindowsServerLicense" \
--description "Windows Server 2019 Datacenter - 50 cores" \
--license-counting-type Core \
--license-count 50 \
--license-count-hard-limit \
--allowed-license-operating-system "Windows"To associate a license configuration with an EC2 instance:
aws license-manager update-license-specifications-for-resource \
--resource-arn arn:aws:ec2:us-east-1:123456789012:instance/i-0abcd1234 \
--add-license-specifications LicenseConfigurationArn=arn:aws:license-manager:us-east-1:123456789012:license-configuration:lic-12345abcdeTo view license consumption:
aws license-manager get-license-configuration \
--license-configuration-arn arn:aws:license-manager:us-east-1:123456789012:license-configuration:lic-12345abcdeSample output:
{
"LicenseConfigurationArn": "arn:aws:license-manager:us-east-1:123456789012:license-configuration:lic-12345abcde",
"LicenseConfigurationId": "lic-12345abcde",
"LicenseCountingType": "Core",
"LicenseCount": 50,
"LicenseCountHardLimit": true,
"ConsumedLicenses": 12,
"Status": "AVAILABLE",
"LicenseRules": [
"allowedTenancy=default",
"allowedInstanceFamilies=m5,r5"
]
}Interaction with Related Technologies
License Manager interacts with: - AWS Systems Manager: For inventory collection and on-premises server management. You must configure Systems Manager Inventory and ensure SSM Agent is running. - AWS Organizations: To centrally manage licenses across multiple accounts. Enable trusted access for License Manager in the management account. - AWS Marketplace: To subscribe to third-party licenses that are managed through License Manager. - Amazon EC2: License Manager can automatically discover EC2 instances and track their license usage. - Amazon RDS: For managing licenses for database engines like SQL Server and Oracle. - AWS CloudTrail: Logs all License Manager API calls for auditing. - Amazon CloudWatch: You can monitor license usage metrics and set alarms.
License Manager vs. AWS Systems Manager Inventory
While both collect inventory, License Manager focuses specifically on license compliance. Systems Manager Inventory provides raw data; License Manager applies your license rules to determine compliance. You can use Systems Manager to gather software inventory, but License Manager adds the license counting and enforcement layer.
Common Exam Scenarios
The SOA-C02 exam tests your ability to:
Choose the correct service for BYOL license management (License Manager vs. Systems Manager vs. AWS Config).
Configure license configurations with appropriate counting rules (per core, per socket, per instance).
Understand that License Manager does not actively enforce license limits—it only reports compliance. You must take action (e.g., stop instances) manually or via automation.
Know that License Manager can track licenses for on-premises servers via Systems Manager.
Recognize that License Manager supports both AWS Marketplace and BYOL licenses.
Limits and Quotas
Maximum license configurations per region: 1000
Maximum license associations per resource: 50
Maximum license configurations per resource: 1 (but a license configuration can be associated with many resources)
API request rate: 10 requests per second per account per region (can be increased).
Pricing
AWS License Manager is free to use. You pay only for the resources it manages (e.g., EC2 instances, Systems Manager inventory). There is no additional charge for creating license configurations or tracking consumption.
Identify License Requirements
First, determine which software licenses you need to manage. For each license type, gather the license agreement terms: the total number of licenses purchased, the counting metric (per core, per socket, per instance, or per user), any restrictions on instance families or tenancy, and expiration dates. For example, a Microsoft Windows Server Datacenter license might be counted per core, limited to 16 cores per instance, and allowed on dedicated or default tenancy. Document these requirements before creating license configurations in AWS License Manager.
Create License Configuration
Using the AWS Management Console, CLI, or SDK, create a license configuration that matches your license agreement. Specify the license name, description, counting type (e.g., Core), total license count (e.g., 100), and set a hard limit if you want to prevent exceeding the count. Add license rules such as allowed instance families (e.g., m5, r5) and allowed tenancy (default or dedicated). Optionally, set an expiration date. Each license configuration is created in a specific AWS region and has a unique ARN.
Associate Resources with License Configuration
Associate your EC2 instances, RDS databases, or on-premises servers with the license configuration. For EC2, you can associate the configuration during instance launch or update an existing instance. For on-premises servers, you must have the Systems Manager Agent installed and the server managed by Systems Manager. Use the AWS CLI command update-license-specifications-for-resource to associate a resource. You can associate multiple resources with the same license configuration, and each resource can be associated with up to 50 license configurations.
Monitor License Consumption
After associations, License Manager automatically tracks license consumption based on the counting rule. For example, if the counting type is per core and you associate an m5.xlarge (4 cores), it consumes 4 licenses. You can view the consumed license count in the License Manager dashboard or via the get-license-configuration CLI command. The dashboard shows total licenses, consumed licenses, and remaining licenses. If you set a hard limit, resources that would exceed the limit are marked as non-compliant but are not automatically stopped.
Manage Compliance and Automation
License Manager reports compliance status but does not automatically enforce limits. To enforce compliance, you can use AWS Config rules or custom automation (e.g., Lambda functions) that react to compliance changes. For example, you can create an AWS Config rule that triggers a Lambda function to stop an EC2 instance if it violates a license rule. You can also set up CloudWatch alarms on license consumption metrics and send notifications via SNS. Regularly review the compliance dashboard and exported reports to ensure you stay within your license entitlements.
Scenario 1: Enterprise Migration of Microsoft SQL Server to AWS
A large financial services company has 500 SQL Server Enterprise Edition core licenses purchased under a Microsoft Enterprise Agreement. They are migrating 200 on-premises SQL Server instances to Amazon RDS for SQL Server. They need to ensure that the total number of cores used across all RDS instances does not exceed 500. Using AWS License Manager, they create a license configuration with counting type 'Core', license count 500, and set a hard limit. They associate each RDS DB instance with this configuration. License Manager automatically tracks the core count based on the DB instance class (e.g., db.r5.large uses 2 cores). The dashboard shows 487 cores consumed. When the DBA team tries to launch another instance requiring 16 cores, License Manager flags it as non-compliant because it would exceed the 500 limit. The team receives a CloudWatch alarm and manually approves only after verifying that some old instances can be decommissioned. This avoids a costly true-up audit with Microsoft.
Scenario 2: Managing Windows Server Licenses Across Multiple Accounts
A global e-commerce company uses AWS Organizations with 50 accounts. They have 1000 Windows Server Datacenter licenses (per core) to distribute across development, test, and production accounts. They enable License Manager trusted access in the management account and create a license configuration in each region where they run EC2 instances. They use AWS CloudFormation StackSets to deploy the license configuration and associations across all accounts. The central IT team monitors total consumption via the License Manager dashboard in the management account. They notice that a development account is using 200 more cores than allocated. They use AWS Config to automatically stop non-compliant instances and notify the development team. This centralized management prevents license overuse and simplifies audit reporting.
Scenario 3: On-Premises License Tracking with Hybrid Deployment
A healthcare provider has a mix of on-premises and AWS workloads running Oracle Database. They have 100 Oracle Processor licenses (per core). They install SSM Agent on their on-premises servers and register them as managed instances in Systems Manager. They create a license configuration for Oracle with counting type 'Core' and associate both EC2 instances and on-premises servers. License Manager reports total consumption across both environments. When they add a new on-premises server with 8 cores, the consumed count increases accordingly. If they accidentally exceed 100 licenses, they receive a compliance alert. This hybrid tracking is critical for maintaining Oracle license compliance, as Oracle audits can impose heavy penalties for under-licensing.
Common Misconfiguration Pitfalls
Not setting a hard limit: Without a hard limit, License Manager only reports consumption but does not flag overuse. This can lead to accidental license violations.
Incorrect counting type: Using 'per instance' when the license is per core can drastically undercount usage. Always verify the license agreement.
Forgetting to associate resources: License Manager only tracks resources that are explicitly associated. If you launch an EC2 instance without association, it won't be counted.
Ignoring on-premises servers: If you have a hybrid environment, you must install SSM Agent and manage the servers via Systems Manager for License Manager to track them.
What SOA-C02 Tests on AWS License Manager (Objective 6.1)
The exam focuses on the following: - Objective 6.1: Implement cost optimization strategies. License Manager is a cost optimization tool because it helps avoid over-purchasing licenses and under-licensing penalties. - Key concepts: License configurations, license counting types (core, socket, instance, user), hard vs. soft limits, association of resources, compliance reporting. - Integration: License Manager works with Systems Manager for inventory and with Organizations for multi-account management. - BYOL support: For Microsoft, Oracle, SAP, and other vendors. - No automatic enforcement: License Manager does not stop resources; it only reports compliance.
Top 3 Wrong Answers Candidates Choose
"License Manager automatically stops non-compliant instances." This is false. License Manager only reports compliance. To stop instances, you must use automation like AWS Config rules or Lambda. Candidates confuse License Manager with AWS Config's auto-remediation.
"License Manager can track licenses for any software." False. License Manager is designed for specific vendors (Microsoft, Oracle, SAP, etc.) and requires predefined license types. For custom software, you may need to use a custom license type, but the service is optimized for enterprise BYOL.
"License Manager replaces the need for Microsoft License Mobility." False. License Manager helps track usage but does not change the underlying license mobility rules. You still need to ensure your license agreement allows deployment on AWS (e.g., License Mobility through Software Assurance).
Specific Numbers, Values, and Terms That Appear on the Exam
License counting types: Core, Socket, Instance, User.
Hard limit vs. soft limit: Hard limit prevents exceeding the count (resource becomes non-compliant); soft limit only warns.
Allowed instance families: e.g., m5, r5, c5. The exam may ask which instance family is allowed.
Maximum license configurations per account: 1000.
License Manager is free; you pay only for underlying resources.
Integration with Systems Manager is required for on-premises servers.
Edge Cases and Exceptions
License Manager does not support all AWS regions; check regional availability.
License Manager does not support all operating systems; it works with Windows, Linux, and some Unix.
For SQL Server on RDS, License Manager tracks licenses based on DB instance class, but you must also ensure your SQL Server license edition matches (e.g., Standard vs. Enterprise).
License Manager does not track licenses for AWS managed services like Amazon Aurora unless you bring your own license.
How to Eliminate Wrong Answers Using the Underlying Mechanism
If a question asks about enforcement, remember that License Manager only reports. Look for answers that mention automation via Lambda or AWS Config for enforcement.
If a question mentions on-premises tracking, the answer must include Systems Manager and SSM Agent.
If a question asks about counting, identify the correct metric based on the license type. For example, Windows Server per core, SQL Server per core, Oracle per core (or per user).
If a question involves multiple accounts, think about AWS Organizations and trusted access.
AWS License Manager helps manage BYOL licenses for Microsoft, Oracle, SAP, and others.
License configurations define counting rules (Core, Socket, Instance, User) and limits.
License Manager only reports compliance; it does not automatically enforce limits.
You must associate resources (EC2, RDS, on-premises) with a license configuration to track usage.
On-premises servers require Systems Manager Agent and management by Systems Manager.
License Manager is free; you pay for underlying resources like EC2 and Systems Manager inventory.
For multi-account environments, enable trusted access in AWS Organizations.
Use AWS Config or Lambda to automate enforcement actions based on compliance state.
These come up on the exam all the time. Here's how to tell them apart.
AWS License Manager
Purpose-built for license compliance tracking.
Enforces license rules (e.g., allowed instance families, hard limits).
Supports license counting types (core, socket, instance, user).
Provides a compliance dashboard and reports.
Integrates with AWS Organizations for multi-account management.
AWS Systems Manager Inventory
General-purpose inventory collection for software and patches.
Does not enforce license rules; only collects raw data.
No built-in license counting; you must analyze data manually.
Provides inventory data but no license-specific dashboard.
Can collect inventory from on-premises servers via SSM Agent.
Mistake
AWS License Manager automatically enforces license limits by stopping instances.
Correct
License Manager only reports compliance; it does not automatically stop or terminate resources. You must use AWS Config rules, Lambda functions, or other automation to enforce limits.
Mistake
License Manager can manage licenses for any third-party software.
Correct
License Manager is designed for specific vendors like Microsoft, Oracle, SAP, and AWS Marketplace offerings. For custom software, you can use a custom license type but the service may not track all nuances.
Mistake
License Manager tracks licenses across all AWS accounts automatically without configuration.
Correct
You must enable trusted access with AWS Organizations and create license configurations in each account or use StackSets to propagate. Cross-account tracking is not automatic.
Mistake
Once you associate a license configuration, License Manager tracks all software on that instance.
Correct
License Manager tracks based on the license configuration's counting rule (e.g., cores). It does not track all installed software; you need separate configurations for different license types.
Mistake
License Manager works with any on-premises server without additional setup.
Correct
On-premises servers must have the SSM Agent installed and be managed by AWS Systems Manager. License Manager pulls inventory from Systems Manager.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
License Manager does not automatically enforce limits; it only reports compliance. To enforce limits, you can create an AWS Config rule that triggers a Lambda function to stop or terminate non-compliant instances. Alternatively, use CloudWatch alarms on license consumption metrics and set up SNS notifications to manually intervene. The exam expects you to know that enforcement is not built-in.
Yes, but only if the on-premises server has the SSM Agent installed and is managed by AWS Systems Manager. You must register the server as a managed instance in Systems Manager. License Manager then collects inventory data (OS, cores, etc.) and tracks license consumption just like for EC2 instances.
License Manager supports four counting types: Core (per processor core), Socket (per physical socket), Instance (per instance, regardless of size), and User (per user). Choose the type that matches your software license agreement. For example, SQL Server Enterprise is typically per core, while Windows Server Datacenter is per core or per instance depending on the edition.
Yes. When you subscribe to a software product on AWS Marketplace that supports License Manager, the license configuration can be automatically created and associated with your instances. You can also bring your own licenses (BYOL) from vendors like Microsoft and Oracle.
You can view license consumption in the AWS License Manager console under the 'License configurations' section. Each configuration shows consumed licenses, total licenses, and compliance status. You can also export reports to Amazon S3 or use the AWS CLI command get-license-configuration to retrieve the ConsumedLicenses field.
If you set a hard limit and the total consumption would exceed the license count, License Manager marks the resource as non-compliant but does not stop it. The resource continues to run. You must manually or automatically take action to bring consumption back under the limit. The hard limit is a reporting threshold, not an enforcement mechanism.
Yes, by enabling trusted access with AWS Organizations. You can then centrally manage license configurations from the management account and view consumption across all member accounts. You can also use AWS CloudFormation StackSets to deploy license configurations to multiple accounts.
You've just covered AWS License Manager — now see how well it sticks with free SOA-C02 practice questions. Full explanations included, no account needed.
Done with this chapter?