Easy ReviewDOP-C02
Configuration Management and IaC9

License Manager

Track software license use and apply rules across AWS and on-premises servers.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

License inventory and rules

AWS License Manager tracks software license use across AWS accounts and Regions and can manage licenses on servers outside AWS. Bring Your Own LicenseUsing existing software licenses for cloud resources. (BYOL) means using existing licenses with cloud resources.

How it works

  1. Review the software agreement and create a self-managed licenseA set of licensing rules based on an enterprise agreement. with rules that reflect its terms.
  2. Select a counting type: virtual CPUs (vCPUs), cores, sockets, or instances. Rules can include tenancy restrictions and license limits. A hard limit prevents deployment when exceeded; a soft limit notifies instead.
  3. Use Systems Manager to manage licenses on servers outside AWS.
Counting type Supported tenancy
Cores or sockets Dedicated HostsA physical server whose instance capacity is dedicated to your use.
Instances or vCPUs Shared, Dedicated Instances, or Dedicated Hosts

Exam cues

  • If the question says reuse existing software licenses on AWS, think BYOL and self-managed licenses, because their rules reflect the agreement.
  • If the question says track licenses on servers outside AWS, think License Manager with Systems Manager, because it can manage those servers’ licenses.
  • If the question says count physical cores or sockets, think Dedicated Hosts, because those counting types require that tenancy.
  • If the question says prevent deployment above a license limit, think a hard limit, because a soft limit only notifies.

Remember

  • Counting types are vCPUs, cores, sockets, and instances.
  • Core and socket counting require Dedicated Hosts.
  • A hard limit prevents deployment when the license limit is exceeded; a soft limit notifies the administrator.

Trap: A soft limit does not prevent deployment when the license limit is exceeded. Choose a hard limit for that.

Da documentação da AWS (11)
  • AWS License Manager tracks software license usage across AWS Regions and accounts and can use Systems Manager to manage licenses on servers outside AWS.
  • Bring Your Own License means repurposing existing license inventory for cloud resources.
  • Self-managed licenses contain rules based on enterprise agreements that determine how AWS processes commands consuming licenses.
  • Self-managed licenses count by vCPUs, cores, sockets, or instances.
  • Core and socket counting require Dedicated Hosts; instance and vCPU counting support shared, Dedicated Host, and Dedicated Instance tenancy.
  • Host affinity applies to core or socket counting for 1 to 180 days; after the period licenses become available for reuse within 24 hours.
  • Querying Systems Manager Inventory requires a Resource Data Sync that stores inventory in an S3 bucket.
  • When a license limit is exceeded, a soft limit notifies the administrator while a hard limit prevents a resource from deploying.
  • Automated discovery uses Systems Manager Inventory and product information in a self-managed license to track instances with matching software.
  • AWS Resource Access Manager can share self-managed licenses with AWS accounts or an organization.
  • Automated discovery of RDS for Oracle or RDS for Db2 uses vCPU counting and does not support rules or hard license limits.

License tracking operations

AWS License Manager can track licenses for on-premises applications alongside AWS servers and monitor usage across accounts and Regions. Inventory search and license asset groupsA group of related assets used to manage and monitor license usage centrally. support these views.

How it works

  1. Use Systems Manager Inventory to discover on-premises applications, attach licensing rules, and refresh non-AWS inventory periodically. License Manager cannot validate those servers’ rules at launch or termination.
  2. Use license asset groups to monitor usage across accounts and Regions. Manage their rules from a management or delegated administrator account.
  3. Review the stopped instances rule and automated discovery behavior. The former controls whether stopped instances count; the latter can be configured to stop tracking instances after software is uninstalled. License rules, automated discovery

Exam cues

  • If the question says track on-premises applications, think Systems Manager Inventory and periodic refresh, because License Manager cannot validate non-AWS servers at launch or termination.
  • If the question says monitor license usage across accounts and Regions, think license asset groups, because they centralize monitoring and rule management.
  • If the question says stop tracking after software uninstall, think automated discovery configuration, because tracking continues by default.

Remember

  • Include stopped instances defaults to false, so their licenses return to the available pool.
  • Automated discovery keeps tracking instances after software uninstall by default.

Trap: Discovering an on-premises application does not mean License Manager validates its licensing rules when the server launches or terminates.

Da documentação da AWS (5)
  • Systems Manager Inventory can discover on-premises applications so licensing rules can be attached and tracked alongside AWS servers.
  • License Manager cannot validate licensing rules for non-AWS servers at launch or termination, and their inventory must be refreshed periodically.
  • License asset groups manage and monitor usage across accounts and Regions, with rules managed from a management or delegated administrator account.
  • The include stopped instances rule defaults to false, releasing stopped instances' licenses back to the available pool.
  • Automated discovery does not stop tracking an instance after software is uninstalled by default, but it can be configured to do so.

Flashcards

toque para virar
Resposta

·

Todos os 9 flashcards em lista

Which AWS service tracks software licenses across AWS and on-premises servers?

AWS License Manager, using Systems Manager for servers outside AWS.

A company wants to apply its software contract rules to licenses used by AWS resources. What AWS License Manager feature should it use?

A self-managed license. Its rules reflect the enterprise agreement and govern commands that consume licenses.

What license counting types does AWS License Manager support for self-managed licenses?

vCPUs, cores, sockets, and instances.

A company counts AWS License Manager licenses by physical sockets. What EC2 tenancy is required?

Dedicated Hosts. Core and socket counting require them.

A company must prevent a new deployment when its AWS License Manager license count would be exceeded. Which limit should it choose?

A hard limit. A soft limit notifies when exceeded but does not prevent deployment.

Does AWS License Manager validate on-premises licensing rules when a server launches or terminates?

No. Use Systems Manager Inventory for discovery, attach rules, and refresh inventory periodically.

A company wants one view of license usage across AWS accounts and Regions. What AWS License Manager feature helps?

License asset groups provide centralized monitoring and rule management.

By default, does AWS License Manager count stopped instances against a self-managed license?

No. The include stopped instances rule defaults to false, releasing their licenses to the pool.

Does AWS License Manager automatically stop tracking an instance when discovered software is uninstalled?

No. Configure automated discovery to stop tracking on uninstall if needed.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!