AWS Organizations
User Guide

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

AWS License Manager and AWS Organizations

AWS License Manager streamlines the process of bringing software vendor licenses to the cloud. As you build out cloud infrastructure on AWS, you can save costs by using bring-your-own-license (BYOL) opportunities—that is, by repurposing your existing license inventory for use with cloud resources. With rule-based controls on the consumption of licenses, administrators can set hard or soft limits on new and existing cloud deployments, stopping noncompliant server usage before it happens. By linking AWS License Manager with AWS Organizations, you can enable cross-account discovery of computing resources throughout your organization. For more information about AWS License Manager, see the AWS License Manager Guide.

The following list provides information that is useful to know when you want to integrate AWS License Manager and AWS Organizations:

  • To enable trusted access with AWS Organizations: You must sign in with your AWS Organizations master account to associate it with your AWS License Manager account and then configure your License Manager settings. For information, see Configuring AWS License Manager Guide Settings.

  • Service principal names for AWS License Manager: license-manager.amazonaws.com and license-manager.member-account.amazonaws.com.

  • Names of the IAM service-linked roles that can be created in accounts when trusted access is enabled: AWSLicenseManagerMasterAccountRole, AWSLicenseManagerMemberAccountRole, and AWSServiceRoleForAWSLicenseManagerRole.

    For more information, see Using the License Manager–Master Account Role and Using the License Manager–Member Account Role.