A self-managed license represents the licensing terms in the agreement with your software vendor. Your self-managed license specifies how your licenses should be counted (for example, by vCPUs or number of instances). It also specifies limits on your usage, so that you can prevent usage from going over the number of allocated licenses. Additionally, it can also specify other constraints on your licenses, such as the tenancy type.
Considerations for Amazon RDS for Oracle and Amazon RDS for Db2 databasesWhen you add product information to configure automated discovery of Amazon RDS for Oracle or Amazon RDS for Db2 databases, the following requirements apply:
The supported license counting type is vCPU.
Rules are not supported.
Hard license limits are not supported.
You can track one product version per self-managed license.
You cannot track Amazon RDS databases and other products using the same self-managed license.
Open the License Manager console at https://console.aws.amazon.com/license-manager/.
In the left navigation pane, choose self-managed licenses.
Choose Create self-managed license.
In the Configuration details panel, provide the following information:
Self-managed license name â A name for the self-managed license.
Description â An optional description of the self-managed license.
License type â The counting model for this license (vCPUs, Cores, Sockets, or Instances).
Number of <option> â The option displayed depends on the license type. When the license limit is exceeded, License Manager notifies you (soft limit) or prevents a resource from deploying (hard limit).
Enforce license limit â If selected, the license limit is a hard limit.
Rules â One or more rules. For each rule, select a rule type, provide a rule value, and choose Add rule. The rule types displayed depend on the license type. For example, minimum values, maximum values, and tenancy. If you do not specify a tenancy type, all are accepted.
(Optional) In the Automated discovery rules panel, do the following:
Choose the product name, product type, and resource type for each product to discover and track using automated discovery.
Select Stop tracking instances when software is uninstalled to make the license available for reuse after License Manager detects that the software was uninstalled and any license affinity period has elapsed.
(Optional) If your account is a License Manager management account for an Organizations you have to option to define resources to exclude from automated discovery. To do so select Add exclusion rule, choose the property to filter on, AWS account IDs and resource Tags are supported, then enter the information to identify that property.
(Optional) Expand the Tags panel to add one or more tags to your self-managed license. Tags are key/value pairs. Provide the following information for each tag:
Key â The searchable name of the key.
Value â The value for the key.
Choose Submit.
Build rules from vendor licenses
Share a self-managed license
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4