AWS License Manager
User Guide

Using the Core License Manager Role

This topic describes the License Manager role, a service-linked role that License Manager requires for its core functions.

Permissions for the Core License Manager Role

License Manager uses the service-linked role named AWSServiceRoleForAWSLicenseManagerRole. This allows License Manager access to AWS resources to manage licenses on your behalf.

The AWSServiceRoleForAWSLicenseManagerRole service-linked role trusts the following service to assume the role:


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:PutObject on arn:aws:s3:::aws-license-manager-service-*

  • Action: sns:Publish on arn:aws:sns:*:*:aws-license-manager-service-*

  • Action: sns:ListTopics on *

  • Action: ec2:DescribeInstances on *

  • Action: ec2:DescribeImages on *

  • Action: ec2:DescribeHosts on *

  • Action: ssm:ListInventoryEntries on *

  • Action: ssm:GetInventory on *

  • Action: ssm:CreateAssociation on *

  • Action: organizations:ListAWSServiceAccessForOrganization on *

  • Action: organizations:DescribeOrganizationon *

{ "Version": "2012-10-17", "Statement": [ { "Sid": "S3BucketPermissions", "Effect": "Allow", "Action": [ "s3:GetBucketLocation", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::aws-license-manager-service-*" ] }, { "Sid": "S3ObjectPermissions", "Effect": "Allow", "Action": [ "s3:PutObject" ], "Resource": [ "arn:aws:s3:::aws-license-manager-service-*" ] }, { "Sid": "SNSAccountPermissions", "Effect": "Allow", "Action": [ "sns:Publish" ], "Resource": [ "arn:aws:sns:*:*:aws-license-manager-service-*" ] }, { "Sid": "SNSTopicPermissions", "Effect": "Allow", "Action": [ "sns:ListTopics" ], "Resource": [ "*" ] }, { "Sid": "EC2Permissions", "Effect": "Allow", "Action": [ "ec2:DescribeInstances", "ec2:DescribeImages", "ec2:DescribeHosts" ], "Resource": [ "*" ] }, { "Sid": "SSMPermissions", "Effect": "Allow", "Action": [ "ssm:ListInventoryEntries", "ssm:GetInventory", "ssm:CreateAssociation" ], "Resource": [ "*" ] }, { "Sid": "OrganizationPermissions", "Effect": "Allow", "Action": [ "organizations:ListAWSServiceAccessForOrganization", "organizations:DescribeOrganization" ], "Resource": [ "*" ] } ] }

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.

Creating a Service-Linked Role for License Manager

You don't need to manually create a service-linked role. When you complete the License Manager first-run experience form the first time that you visit the License Manager console, the service-linked role is automatically created for you.

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.


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 AWSServiceRoleForAWSLicenseManagerRole 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 the License Manager console to create a service-linked role.

To create a service-linked role

  1. Open the License Manager console at

  2. Choose Start using License Manager.

  3. In the IAM Permissions (one-time-setup) form, select I grant AWS License Manager the required permissions, then choose Continue.

You can also use the IAM console to create a service-linked role with the License Manager use case. In the AWS CLI or the AWS API, use IAM to create a service-linked role with the 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 AWSServiceRoleForAWSLicenseManagerRole 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

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.

Cleaning Up a Service-Linked Role

Before you can use IAM to delete a service-linked role, you must first delete all resources used by the role. This means disassociating any license configurations from associated instances and AMIs, and then deleting the license configurations.


If License Manager is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.

To delete License Manager resources used by the AWSServiceRoleForAWSLicenseManagerRole

  1. Open the License Manager console at

  2. In the navigation pane, choose License configuration.

  3. For a specific license configuration for which you are the owner, disassociate all associated AMIs and resources.

  4. While still on the license configuration page, delete the license configuration.

  5. Repeat steps 2 and 3 until all license configurations have been deleted.

Manually Delete the Service-Linked Role

Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAWSLicenseManagerRole service-linked role. If you are also using AWSLicenseManagerMasterAccountRole and AWSLicenseManagerMemberAccountRole, delete those roles first. 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.

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