[ aws . license-manager ]
Creates a license configuration.
A license configuration is an abstraction of a customer license agreement that can be consumed and enforced by License Manager. Components include specifications for the license type (licensing by instance, socket, CPU, or vCPU), allowed tenancy (shared tenancy, Dedicated Instance, Dedicated Host, or all of these), host affinity (how long a VM must be associated with a host), and the number of licenses purchased and used.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
create-license-configuration
--name <value>
[--description <value>]
--license-counting-type <value>
[--license-count <value>]
[--license-count-hard-limit | --no-license-count-hard-limit]
[--license-rules <value>]
[--tags <value>]
[--product-information-list <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--cli-auto-prompt <value>]
--name
(string)
Name of the license configuration.
--description
(string)
Description of the license configuration.
--license-counting-type
(string)
Dimension used to track the license inventory.
Possible values:
vCPU
Instance
Core
Socket
--license-count
(long)
Number of licenses managed by the license configuration.
--license-count-hard-limit
| --no-license-count-hard-limit
(boolean)
Indicates whether hard or soft license enforcement is used. Exceeding a hard limit blocks the launch of new instances.
--license-rules
(list)
License rules. The syntax is #name=value (for example, #allowedTenancy=EC2-DedicatedHost). Available rules vary by dimension.
Cores
dimension:allowedTenancy
|maximumCores
|minimumCores
Instances
dimension:allowedTenancy
|maximumCores
|minimumCores
|maximumSockets
|minimumSockets
|maximumVcpus
|minimumVcpus
Sockets
dimension:allowedTenancy
|maximumSockets
|minimumSockets
vCPUs
dimension:allowedTenancy
|honorVcpuOptimization
|maximumVcpus
|minimumVcpus
(string)
Syntax:
"string" "string" ...
--tags
(list)
Tags to add to the license configuration.
(structure)
Details about a tag for a license configuration.
Key -> (string)
Tag key.
Value -> (string)
Tag value.
Shorthand Syntax:
Key=string,Value=string ...
JSON Syntax:
[
{
"Key": "string",
"Value": "string"
}
...
]
--product-information-list
(list)
Product information.
(structure)
Describes product information for a license configuration.
ResourceType -> (string)
Resource type. The value is
SSM_MANAGED
.ProductInformationFilterList -> (list)
Product information filters. The following filters and logical operators are supported:
Application Name
- The name of the application. Logical operator isEQUALS
.
Application Publisher
- The publisher of the application. Logical operator isEQUALS
.
Application Version
- The version of the application. Logical operator isEQUALS
.
Platform Name
- The name of the platform. Logical operator isEQUALS
.
Platform Type
- The platform type. Logical operator isEQUALS
.
License Included
- The type of license included. Logical operators areEQUALS
andNOT_EQUALS
. Possible values aresql-server-enterprise
|sql-server-standard
|sql-server-web
|windows-server-datacenter
.(structure)
Describes product information filters.
ProductInformationFilterName -> (string)
Filter name.
ProductInformationFilterValue -> (list)
Filter value.
(string)
ProductInformationFilterComparator -> (string)
Logical operator.
JSON Syntax:
[
{
"ResourceType": "string",
"ProductInformationFilterList": [
{
"ProductInformationFilterName": "string",
"ProductInformationFilterValue": ["string", ...],
"ProductInformationFilterComparator": "string"
}
...
]
}
...
]
--cli-input-json
| --cli-input-yaml
(string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton
. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml
.
--generate-cli-skeleton
(string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input
, prints a sample input JSON that can be used as an argument for --cli-input-json
. Similarly, if provided yaml-input
it will print a sample input YAML that can be used with --cli-input-yaml
. If provided with the value output
, it validates the command inputs and returns a sample output JSON for that command.
--cli-auto-prompt
(boolean)
Automatically prompt for CLI input parameters.
See ‘aws help’ for descriptions of global parameters.
Example 1: To create a license configuration
The following create-license-configuration
example creates a license configuration with a hard limit of 10 cores.
aws license-manager create-license-configuration --name my-license-configuration \
--license-counting-type Core \
--license-count 10 \
--license-count-hard-limit
Output:
{
"LicenseConfigurationArn": "arn:aws:license-manager:us-west-2:123456789012:license-configuration:lic-6eb6586f508a786a2ba41EXAMPLE1111"
}
Example 2: To create a license configuration
The following create-license-configuration
example creates a license configuration with a soft limit of 100 vCPUs. It uses a rule to enable vCPU optimization.
aws license-manager create-license-configuration --name my-license-configuration
--license-counting-type vCPU \
--license-count 100 \
--license-rules "#honorVcpuOptimization=true"
Output:
{
"LicenseConfigurationArn": "arn:aws:license-manager:us-west-2:123456789012:license-configuration:lic-6eb6586f508a786a2ba41EXAMPLE2222"
}
LicenseConfigurationArn -> (string)
Amazon Resource Name (ARN) of the license configuration.