Module types 

Data structures used by operation inputs/outputs.

Modules

builders

Builders

error

Error types that AWS License Manager can respond with.

Structs

AndRuleStatement

AND rule statement.

Asset

Asset.

AutomatedDiscoveryInformation

Describes automated discovery.

BorrowConfiguration

Details about a borrow configuration.

ConsumedLicenseSummary

Details about license consumption.

ConsumptionConfiguration

Details about a consumption configuration.

CrossAccountDiscoveryServiceStatus

Status information for cross-account discovery service.

CrossRegionDiscoveryStatus

Status information for cross-region discovery.

DatetimeRange

Describes a time range, in ISO8601-UTC format.

Entitlement

Describes a resource entitled for use with a license.

EntitlementData

Data associated with an entitlement resource.

EntitlementUsage

Usage associated with an entitlement resource.

Filter

A filter name and value pair that is used to return more specific results from a describe operation. Filters can be used to match a set of resources by specific criteria, such as tags, attributes, or IDs.

Grant

Describes a grant.

GrantedLicense

Describes a license that is granted to a grantee.

InstanceRuleStatement

Instance rule statement.

InventoryFilter

An inventory filter.

Issuer

Details about the issuer of a license.

IssuerDetails

Details associated with the issuer of a license.

License

Software license that is managed in License Manager.

LicenseAssetGroup

License asset group.

LicenseAssetGroupConfiguration

License asset group configuration.

LicenseAssetGroupProperty

License asset group property.

LicenseAssetRule

License asset rule.

LicenseAssetRuleset

License asset ruleset.

LicenseConfiguration

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.

LicenseConfigurationAssociation

Describes an association with a license configuration.

LicenseConfigurationRuleStatement

License configuration rule statement.

LicenseConfigurationUsage

Details about the usage of a resource associated with a license configuration.

LicenseConversionContext

Information about a license type conversion task.

LicenseConversionTask

Information about a license type conversion task.

LicenseOperationFailure

Describes the failure of a license operation.

LicenseRuleStatement

License rule statement.

LicenseSpecification

Details for associating a license configuration with a resource.

LicenseUsage

Describes the entitlement usage associated with a license.

ManagedResourceSummary

Summary information about a managed resource.

MatchingRuleStatement

Matching rule statement.

Metadata

Describes key/value pairs.

Options

The options you can specify when you create a new version of a grant, such as activation override behavior. For more information, see Granted licenses in License Manager in the License Manager User Guide.

OrRuleStatement

OR rule statement.

OrganizationConfiguration

Configuration information for Organizations.

ProductCodeListItem

A list item that contains a product code.

ProductInformation

Describes product information for a license configuration.

ProductInformationFilter

Describes product information filters.

ProvisionalConfiguration

Details about a provisional configuration.

ReceivedMetadata

Metadata associated with received licenses and grants.

RegionStatus

Status information for a specific region.

ReportContext

Details of the license configuration that this generator reports on.

ReportFrequency

Details about how frequently reports are generated.

ReportGenerator

Describe the details of a report generator.

ResourceInventory

Details about a resource.

RuleStatement

Rule statement.

S3Location

Details of the S3 bucket that report generator reports are published to.

ScriptRuleStatement

Rule statement that uses a script to evaluate license asset conditions.

ServiceStatus

Overall service status information for License Manager.

Tag

Details about the tags for a resource. For more information about tagging support in License Manager, see the TagResource operation.

TokenData

Describes a token.

Enums

ActivationOverrideBehavior

When writing a match expression against ActivationOverrideBehavior, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

AllowedOperation

When writing a match expression against AllowedOperation, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

CheckoutType

When writing a match expression against CheckoutType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

DigitalSignatureMethod

When writing a match expression against DigitalSignatureMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

EntitlementDataUnit

When writing a match expression against EntitlementDataUnit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

EntitlementUnit

When writing a match expression against EntitlementUnit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

GrantStatus

When writing a match expression against GrantStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

InventoryFilterCondition

When writing a match expression against InventoryFilterCondition, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseAssetGroupStatus

When writing a match expression against LicenseAssetGroupStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseConfigurationStatus

When writing a match expression against LicenseConfigurationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseConversionTaskStatus

When writing a match expression against LicenseConversionTaskStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseCountingType

When writing a match expression against LicenseCountingType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseDeletionStatus

When writing a match expression against LicenseDeletionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

LicenseStatus

When writing a match expression against LicenseStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ProductCodeType

When writing a match expression against ProductCodeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ReceivedStatus

When writing a match expression against ReceivedStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

RenewType

When writing a match expression against RenewType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ReportFrequencyType

When writing a match expression against ReportFrequencyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ReportType

When writing a match expression against ReportType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ResourceType

When writing a match expression against ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

TokenType

When writing a match expression against TokenType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.