View a markdown version of this page

Conversion prerequisites for License Manager license types - Amazon License Manager
GeneralWindowsLinux
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Conversion prerequisites for License Manager license types

To convert license types with License Manager, there are general and operating system specific prerequisites.

General

You must meet the following general prerequisites before performing a license type conversion:

  • Your Amazon Web Services account must be onboarded to License Manager. See Get started with License Manager.

  • The target instance must run on Amazon. On-premises instances are not supported.

  • The target instance must be in the stopped state before you convert the license type. For more information, see Stop and start your instance in the Amazon EC2 User Guide.

  • If stop protection is enabled on the target instance, the conversion process will fail. For more information, see Troubleshooting license type conversion in License Manager.

  • The target instance must be configured with Amazon Systems Manager Inventory. For more information, see Setting up Systems Manager for EC2 instances and Amazon Systems Manager Inventory in the Amazon Systems Manager User Guide.

  • Your user or role must have the following permissions:

    • ssm:GetInventory

    • ssm:StartAutomationExecution

    • ssm:GetAutomationExecution

    • ssm:SendCommand

    • ssm:GetCommandInvocation

    • ssm:DescribeInstanceInformation

    • ec2:DescribeImages

    • ec2:DescribeInstances

    • ec2:StartInstances

    • ec2:StopInstances

    • license-manager:CreateLicenseConversionTaskForResource

    • license-manager:GetLicenseConversionTask

    • license-manager:ListLicenseConversionTasks

    • license-manager:GetLicenseConfiguration

    • license-manager:ListUsageForLicenseConfiguration

    • license-manager:ListLicenseSpecificationsForResource

    • license-manager:ListAssociationsForLicenseConfiguration

    • license-manager:ListLicenseConfigurations

    For more information about Systems Manager Inventory, see Amazon Systems Manager Inventory.

Windows

Windows instances must meet the following prerequisites:

  • Instances that were originally launched from an Amazon provided Amazon Machine Image (AMI) are not eligible for license type conversion to BYOL. The original Amazon EC2 instance must be launched from your own virtual machine (VM) image. For more information about converting a VM to Amazon EC2, see VM Import/Export.

  • To change your SQL Server license to BYOL, SQL Server must have been installed using your own media.

Linux

Linux instances must meet the following prerequisites:

RHEL

  • If converting from Amazon-provided subscriptions to subscriptions sold by Red Hat as an AMI listing on Amazon Web Services Marketplace, you must first subscribe to the Marketplace AMI listing from Red Hat before initiating the license conversion.

  • For transitions from Amazon-provided subscriptions to the Red Hat Subscriptions SaaS listing on Amazon Web Services Marketplace you'll need to purchase subscriptions from Red Hat prior to conversion.

RHEL for SAP

  • For RHEL for SAP and Update Services conversions, instances must be launched from Amazon Web Services Marketplace with a RunInstance:0010 usage operation and an attached Amazon Web Services Marketplace product code.

  • If converting from Amazon-provided subscriptions to subscriptions sold by Red Hat as an AMI listing on Amazon Web Services Marketplace, you must first subscribe to the Marketplace AMI listing from Red Hat before initiating the license conversion.

  • For transitions from Amazon-provided subscriptions to the Red Hat Subscriptions SaaS listing on Amazon Web Services Marketplace you'll need to purchase subscriptions from Red Hat prior to conversion.

Ubuntu

  • Instances must be running Ubuntu LTS.

  • If you are converting to Ubuntu Pro sold by Canonical in Amazon Web Services Marketplace, you must have an active Canonical Ubuntu Pro subscription in Amazon Web Services Marketplace before you initiate the conversion. If you don't have an existing subscription, you can subscribe to the Canonical Ubuntu Pro general listing when you convert using the License Manager console. This requirement does not apply when you convert to Ubuntu Pro provided by Amazon (usage operation RunInstances:0g00).

  • If you are converting to Ubuntu Pro sold by Canonical in Amazon Web Services Marketplace, the instance's architecture and instance type must be supported by the Canonical Ubuntu Pro Amazon Web Services Marketplace listing that you convert to. To check which architectures and instance types a listing supports, see the listing's Usage information in Amazon Web Services Marketplace. Because each listing supports a specific architecture, instances with different architectures (x86_64 and Arm) must be converted in separate conversion tasks. This requirement does not apply when you convert to Ubuntu Pro provided by Amazon.

  • The Ubuntu Pro Client must be installed in your Ubuntu operating system.

    • Run the following command to confirm if the Ubuntu Pro Client is installed:

      pro --version

    • If the command is not found, or the version needs to be updated, run the following command to install the Ubuntu Pro Client:

      apt-get update && apt-get dist-upgrade

  • Instances must be able to reach multiple endpoints to activate their Ubuntu Pro subscription and receive updates. You must allow outbound traffic from your instance over TCP port 443 to reach the following endpoints:

    • contracts.canonical.com – Used for Ubuntu Pro activation.

    • esm.ubuntu.com – Used for APT repository access for most services.

    • api.snapcraft.io – Used for installing and running snaps.

    • dashboard.snapcraft.io – Used for installing and running snaps.

    • login.ubuntu.com – Used for installing and running snaps.

    • cloudfront.cdn.snapcraftcontent.com – Used for downloading from content development networks (CDNs).

    • livepatch.canonical.com – Used for downloading patches from the Livepatch server.

    For more information, see Ubuntu Pro Client network requirements in the Ubuntu Pro Client documentation and Network requirements in the Canonical Snapcraft documentation.