AWS License Manager
User Guide

Using the License Manager–Member Account Role

This topic describes License Manager–Member Account, the service-linked role that License Manager requires to allow the master account to manage licenses.

Permissions for License Manager–Member Account Role

License Manager–Member Account uses the service-linked role named AWSServiceRoleForAWSLicenseManagerMemberAccountRole. This role allows License Manager to access AWS resources for license management operations from a configured master account on your behalf.

The AWSServiceRoleForAWSLicenseManagerMemberAccountRole service-linked role trusts the following services to assume the role:

  • license-manager.member-account.amazonaws.com

The role permissions policy allows License Manager to complete the following actions on the specified resources:

  • Action: license-manager:UpdateLicenseSpecificationsForResource on *

  • Action: ssm:ListInventoryEntries on *

  • Action: ssm:GetInventory on *

  • Action: ssm:CreateAssociation on *

  • Action: ssm:CreateResourceDataSync on *

  • Action: ssm:DeleteResourceDataSync on *

  • Action: ssm:ListResourceDataSync on *

  • Action: ssm:ListAssociations on *

  • Action: ram:AcceptResourceShareInvitation on *

  • Action: ram:GetResourceShareInvitations on *

You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the IAM User Guide.

{ "Version": "2012-10-17", "Statement": [ { "Sid": "LicenseManagerPermissions", "Effect": "Allow", "Action": [ "license-manager:UpdateLicenseSpecificationsForResource" ], "Resource": [ "*" ] }, { "Sid": "SSMPermissions", "Effect": "Allow", "Action": [ "ssm:ListInventoryEntries", "ssm:GetInventory", "ssm:CreateAssociation", "ssm:CreateResourceDataSync", "ssm:DeleteResourceDataSync", "ssm:ListResourceDataSync", "ssm:ListAssociations" ], "Resource": [ "*" ] }, { "Sid": "RAMPermissions", "Effect": "Allow", "Action": [ "ram:AcceptResourceShareInvitation", "ram:GetResourceShareInvitations" ], "Resource": [ "*" ] } ] }

Creating a Service-Linked Role for License Manager–Member Account

You don't need to manually create a service-linked role. When you enable integration with AWS Organizations from the master account in the License Manager console on the Settings page, the AWS CLI using update-service-settings, or the AWS API using UpdateServiceSettings, License Manager creates the service-linked role for you in the Organizations member accounts.

If you delete this service-linked role and then need to create it again, you can use the same process to re-create the role in your account.

You can also use the IAM console, AWS CLI, or IAM API to create a service-linked role manually. For more information, see Creating a Service-Linked Role in the IAM User Guide.

Important

This service-linked role can appear in your account if you completed an action in another service that uses the features supported by this role. If you were using the License Manager service before January 1, 2017, when it began supporting service-linked roles, then License Manager created the AWSServiceRoleForAWSLicenseManagerMemberAccountRole role in your account. For more information, see A New Role Appeared in My IAM Account.

Creating a Service-Linked Role in License Manager

You can use License Manager commands from the AWS Command Line Interface to create a service-linked role.

To create a service-linked role

  1. Log into your AWS Organizations master account.

  2. Open the License Manager console at https://console.aws.amazon.com/license-manager/.

  3. In the left navigation pane, choose Settings, Edit.

  4. Choose Link AWS Organization accounts.

  5. Choose Apply. This creates the roles AWSServiceRoleForAWSLicenseManagerRole and AWSServiceRoleForAWSLicenseManagerMemberAccountRole in all child accounts.

You can also use the IAM console to create a service-linked role with the License Manager - Member Account use case. In the AWS CLI or AWS API, create a service-linked role with the license-manager.member-account.amazonaws.com service name. For more information, see Creating a Service-Linked Role in the IAM User Guide.

If you delete this service-linked role, you can use the same IAM process to create the role again.

Editing a Service-Linked Role for License Manager

License Manager does not allow you to edit the AWSServiceRoleForAWSLicenseManagerMemberAccountRole service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a Service-Linked Role in the IAM User Guide.

Deleting a Service-Linked Role for License Manager

You don't need to manually delete the AWSServiceRoleForAWSLicenseManagerMemberAccountRole role. When you CompleteThisDeleteActionInThisService-3 in the AWS Management Console, AWS CLI, or AWS API, License Manager cleans up the resources and deletes the service-linked role for you.

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way, you only have entities that are actively monitored or maintained. However, you must clean up your service-linked role before you can manually delete it.

Manually Delete the Service-Linked Role

Use the IAM console, AWS CLI, or AWS API to delete the AWSServiceRoleForAWSLicenseManagerMemberAccountRole service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide.

Supported Regions for License Manager Service-Linked Roles

License Manager supports using service-linked roles in all of the Regions where the service is available. For more information, see AWS Regions and Endpoints.

License Manager does not support using service-linked roles in every Region where the service is available. You can use the AWSServiceRoleForAWSLicenseManagerMemberAccountRole role in the following Regions.

Region name Region identity Support in License Manager
US East (N. Virginia) us-east-1 Yes
US East (Ohio) us-east-2 Yes
US West (N. California) us-west-1 No
US West (Oregon) us-west-2 Yes
Asia Pacific (Mumbai) ap-south-1 Yes
Asia Pacific (Osaka-Local) ap-northeast-3 No
Asia Pacific (Seoul) ap-northeast-2 Yes
Asia Pacific (Singapore) ap-southeast-1 Yes
Asia Pacific (Sydney) ap-southeast-2 Yes
Asia Pacific (Tokyo) ap-northeast-1 Yes
Canada (Central) ca-central-1 No
EU (Frankfurt) eu-central-1 Yes
EU (Ireland) eu-west-1 Yes
EU (London) eu-west-2 Yes
EU (Paris) eu-west-3 No
South America (São Paulo) sa-east-1 No
AWS GovCloud (US) us-gov-west-1 No