AWS License Manager
User Guide

Using the License Manager–Master Account Role

This topic describes License Manager–Master Account, the service-linked role that License Manager requires to perform centralized, cross-account, license management.

Permissions for License Manager–Master Account Role

License Manager–Master Account uses the service-linked role named AWSServiceRoleForAWSLicenseManagerMasterAccountRole. The role allows License Manager access to AWS resources to manage license management operations for a central master account on your behalf.

The AWSServiceRoleForAWSLicenseManagerMasterAccountRole service-linked role trusts the following service to assume the roles:

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

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

  • Action: s3:GetBucketLocation on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:ListBucket on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:GetLifecycleConfiguration on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:PutLifecycleConfiguration on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:GetBucketPolicy on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:PutBucketPolicy on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:AbortMultipartUpload on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:PutObject on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:GetObject on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:ListBucketMultipartUploads on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:ListMultipartUploadParts on arn:aws:s3:::aws-license-manager-service-*

  • Action: s3:DeleteObject on arn:aws:s3:::aws-license-manager-service-*/resource_sync/*

  • Action: athena:GetQueryExecution on *

  • Action: athena:GetQueryResults on *

  • Action: athena:StartQueryExecution on *

  • Action: glue:GetTable on *

  • Action: glue:GetPartition on *

  • Action: glue:GetPartitions on *

  • Action: organizations:DescribeOrganization on *

  • Action: organizations:ListAccounts on *

  • Action: organizations:DescribeAccount on *

  • Action: organizations:ListChildren on *

  • Action: organizations:ListParents on *

  • Action: organizations:ListAccountsForParent on *

  • Action: organizations:ListRoots on *

  • Action: organizations:ListAWSServiceAccessForOrganization on *

  • Action: ram:GetResourceShares on *

  • Action: ram:GetResourceShareAssociations on *

  • Action: ram:TagResource on *

  • Action: ram:CreateResourceShare on *

  • Action: ram:AssociateResourceShare on *

  • Action: ram:DisassociateResourceShare on *

  • Action: ram:UpdateResourceShare on *

  • Action: ram:DeleteResourceShare 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": "S3BucketPermissions", "Effect": "Allow", "Action": [ "s3:GetBucketLocation", "s3:ListBucket", "s3:GetLifecycleConfiguration", "s3:PutLifecycleConfiguration", "s3:GetBucketPolicy", "s3:PutBucketPolicy" ], "Resource": [ "arn:aws:s3:::aws-license-manager-service-*" ] }, { "Sid": "S3ObjectPermissions1", "Effect": "Allow", "Action": [ "s3:AbortMultipartUpload", "s3:PutObject", "s3:GetObject", "s3:ListBucketMultipartUploads", "s3:ListMultipartUploadParts" ], "Resource": [ "arn:aws:s3:::aws-license-manager-service-*" ] }, { "Sid": "S3ObjectPermissions2", "Effect": "Allow", "Action": [ "s3:DeleteObject" ], "Resource": [ "arn:aws:s3:::aws-license-manager-service-*/resource_sync/*" ] }, { "Sid": "AthenaPermissions", "Effect": "Allow", "Action": [ "athena:GetQueryExecution", "athena:GetQueryResults", "athena:StartQueryExecution" ], "Resource": [ "*" ] }, { "Sid": "GluePermissions", "Effect": "Allow", "Action": [ "glue:GetTable", "glue:GetPartition", "glue:GetPartitions" ], "Resource": [ "*" ] }, { "Sid": "OrganizationPermissions", "Effect": "Allow", "Action": [ "organizations:DescribeOrganization", "organizations:ListAccounts", "organizations:DescribeAccount", "organizations:ListChildren", "organizations:ListParents", "organizations:ListAccountsForParent", "organizations:ListRoots", "organizations:ListAWSServiceAccessForOrganization" ], "Resource": [ "*" ] }, { "Sid": "RAMPermissions1", "Effect": "Allow", "Action": [ "ram:GetResourceShares", "ram:GetResourceShareAssociations", "ram:TagResource" ], "Resource": [ "*" ] }, { "Sid": "RAMPermissions2", "Effect": "Allow", "Action": [ "ram:CreateResourceShare" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:RequestTag/Service": "LicenseManager" } } }, { "Sid": "RAMPermissions3", "Effect": "Allow", "Action": [ "ram:AssociateResourceShare", "ram:DisassociateResourceShare", "ram:UpdateResourceShare", "ram:DeleteResourceShare" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "ram:ResourceTag/Service": "LicenseManager" } } } ] }

Creating a License Manager–Master Account Service-Linked Role

You don't need to manually create this service-linked role. When you configure cross-account license management in the AWS Management Console, License Manager creates the service-linked role for you.

Note

To make use of cross-account support in License Manager, you must be using AWS Organizations.

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 License Manager before January 1, 2017, when it began supporting service-linked roles, then License Manager created the AWSServiceRoleForAWSLicenseManagerMasterAccountRole role in your account. For more information, see A New Role Appeared in My IAM Account.

Creating a License Manager–Master Account Service-Linked Role

You can use the License Manager console to create this service-linked role.

To create a service-linked role

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

  2. Choose Settings, Edit.

  3. Choose Link AWS Organization accounts.

  4. Choose Apply.

You can also use the IAM console to create a service-linked role with the License Manager–Master Account use case. In the AWS CLI or the AWS API, use IAM to create a service-linked role with the license-manager.master-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 AWSServiceRoleForAWSLicenseManagerMasterAccountRole 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 AWSServiceRoleForAWSLicenseManagerMasterAccountRole role. When you CompleteThisDeleteActionInThisService-2 in the AWS Management Console, the AWS CLI, or the 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 AWSServiceRoleForAWSLicenseManagerMasterAccountRole 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 AWSServiceRoleForAWSLicenseManagerMasterAccountRole 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