AWS License Manager FAQs

License Manager reduces the risk of non-compliance by increasing transparency, and enforcing and tracking licensing rules that administrators define. License Manager provides built-in dashboards that can be used when considering new license purchases, reporting to procurement, and in vendor audits. However, customers are responsible for compliance and assume the responsibility of carefully understanding and adding rules into License Manager based on their licensing agreements. While AWS cannot participate in audits, License Manager’s rich report provides valuable insights that help attain more accuracy and transparency.

When you purchase software licenses in AWS Marketplace, you can track them in License Manager managed entitlements. You can distribute different tiers of licenses to different groups of users (for example, business units) you create in the software, whenever tiered licenses are available from supported vendors.

Yes, you can use managed entitlements with other AWS services such as AWS Service Catalog to simplify deployments and governance of licensed software. This also applies to third-party software licenses purchased in AWS Marketplace, which are automatically created in License Manager. You can use managed entitlements with Identity and Access Management (IAM) or with AWS accounts to control which workloads and users can use those licenses.

When you purchase licenses from participating independent software vendors (ISVs) in AWS Marketplace, you can extend license management across both AWS Cloud accounts and on-premises environments. You can pay for software licenses through AWS Marketplace, and then manage distribution and track entitlements using managed entitlements.

Yes, you can turn on the AWS Organizations integration in License Manager. Using the management account, you can now view all licenses distributed to identities in your AWS Organization across all AWS Regions. You can see detailed information about each license, including the expiration date and software capabilities. You also get metrics showing how much of the license is consumed by each identity.

You can onboard directly through License Manager by creating a public and private key pair through the console or application programming interface (API). License information returned by the API operations is signed with your private key and you can use the public key to verify the signature. Using AWS License Manager’s API operations, you can integrate with your sales order system to create licenses for customers after their purchase and update licenses after renewals. You can also use the API operations to migrate existing licenses from your current system to AWS License Manager. You will need to modify your software to call the API operations to verify a customer’s license before provisioning software capabilities. To simplify integration with the APIs, use the API operations, use AWS SDK.

Yes. License Manager helps you enforce license use by tracking the number of software capabilities customers are using against the amount they are entitled. License Manager tracks usage across all of the customer identities with access to the licenses. When customers stop using your software, they can return the licenses back to the pool and make them available for reuse through the API operations or let the licenses expire automatically.

You can use License Manager to assign licenses to users. For example, a customer might want to give a license with more capabilities to power users, and a different license to the average user. You can enable this by mapping your users to  IAM roles with Amazon Cognito, and then using License Manager to distribute the licenses to those users by specifying their associated IAM roles.

Customers do not have to use AWS Identity with their on-premises applications. You can use License Manager to create a unique short lived token to identify the customer to whom you are giving a license. Next, share this token with the customer. When they launch your software, the customer enters the token to activate the license. Your software should pass the short lived token to the API operations and exchange it for a long lived customer identifier that you use in API calls. For on-premises workloads that do not have an internet connection, you can generate a license file unique to the host that customers can use to run your software on that host.

You can get started with automated discovery by specifying the product information along with licensing rules in License Manager. Product information might include the name of the software, the publisher, and the version, which tells License Manager how to detect installed software.

Consider having an organization-wide tagging strategy that can help you organize your resources, allocate cost, automate processes, control access, and manage security risk. If you are new to tagging, review AWS recommended tagging best practices to learn how to set up and search using tags.

Yes, you can search instances running AWS license Included software.

Yes, you can combine a tag-based search with other search filters that License Manager supports. Other search filters include names of operating systems and applications, whether they are license Included or not, or AWS account IDs, and resource IDs.

Automated discovery helps you track all instances as you install software. If software is specified in automated discovery rules, the instances will automatically get tracked by License Manager. Once you uninstall software,  License Manager will automatically stop tracking those instances and make the licenses available to you for reuse.

Yes, you need to opt in. You can opt in by specifying a simple setting in automated discovery thatwill ask License Manager to stop tracking an instance when applications are uninstalled. See the documentation.

If you install the software again, License Manager’s automated discovery capability will detect it and account for the license usage again.

If your licenses are node-locked to a physical server, you can use License Manager’s license affinity property where you can specify the time period for which your licenses need to be node-locked. License Manager will continue to account for the usage until the license affinity period has elapsed, even if you uninstall your software.

Here are steps to get started. For more information on the prerequisites, see our
documentation.

• Step 1: Configure AWS Directory Service for Microsoft Active Directory.
• Step 2: Subscribe to a product in AWS Marketplace or the EC2 Console.
• Step 3: Launch an instance.
• Step 4: Associate users to an instance.
• Step 5: Connect to a user-based subscription instance

AWS will bill you through a monthly subscription, based on the number of users associated with the license included Microsoft Office or Visual Studio instances. These per-user charges are billed per calendar month, and the billing starts from the time you subscribe to the product. If you remove access to a user during the existing month, you will be billed for the user for the remainder of the month. You will stop incurring charges for the user the following month.

No, a user is only counted once. You get charged per user for Microsoft Office and Visual Studio, irrespective of the number of EC2 instances the user connects. However, Windows Server licenses are bundled with the EC2 instances and are charged per vCPU along with the instance charges.

All EC2 instances that are Nitro based support license included Microsoft Office and Visual Studio.

Linux subscriptions in AWS License Manager helps you view and manage commercial Linux subscriptions that your Amazon EC2 instances use. You can track utilization of your Linux subscriptions for the AWS Regions and accounts in AWS Organizations that you have defined in your settings. License Manager gives you a comprehensive view of your running instances that use Linux subscriptions.

Red Hat Enterprise Linux (RHEL), RHEL Bring Your Own Subscription model (BYOS) with the Red Hat Cloud Access Program, SUSE Linux Enterprise Server, and Ubuntu Pro.

To get started with Linux subscriptions you must visit License Manager settings to configure the regions in which you want to discover and track subscriptions. You can opt to aggregate subscription data across your accounts in AWS Organizations. Initial discovery will complete within 36 hours after which you should see discovered subscriptions and instances.

RHSM discovery uses data from Red Hat Subscription Manager to discover RHEL instances on AWS. RHSM discovery helps you discover RHEL instances that do not have metadata to identify them, such as bring your own subscription (BYOS) instances based on custom images. Activating RHSM discovery provides more detailed information about RHEL BYOS instances such as Red Hat release version and gives you a consolidated view of all your RHEL instances in use on AWS. You can activate RHSM discovery in Linux subscriptions settings.

To see usage of Linux subscriptions and setup notifications based on thresholds, look at the subscriptions view of the subscription you are interested in. There you can see usage over time and create alarms based on thresholds you set. Alarms are set as AWS Cloud Watch notifications so you receive them in the same way you do other notifications.

Yes, you can use either the License Manager Console or the AWS CLI to convert the license type of eligible Ubuntu LTS instances. Instances must be stopped and associated by AWS Systems Manager Inventory. See License Manager documentation for more information about Ubuntu LTS license conversion.

There is no additional charge for using License Manager. You pay for only the resources created in your account. These include Amazon Elastic Compute Cloud (EC2) instances but can also include an Amazon Simple Storage Service (S3) bucket for storing software based on AWS Systems Manager. It can also include Amazon Athena queries, and AWS Glue jobs for enabling the centralized discovery of the Systems Manager data, and Amazon Simple Notification Service (SNS) notifications.