AWS License Manager

Name: AWS License Manager API
Brand: AWS License Manager
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputehmac50 Endpoints

Install Jentic One Beta

Connect the AWS License Manager to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS License Manager, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS License Manager API.

Create licence configurations that define seat counts and rules

Issue, check out, and check in licences via /CheckoutLicense and /CheckInLicense

Share licences across accounts with grants and grant versions

GET STARTED

Start building with AWS License Manager API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AWS License Manager API for, with concrete tasks.

★ BYOL Software Tracking

Track bring-your-own-licence software running on EC2 dedicated hosts and on-premises servers. License Manager configurations define rules such as core counts and tenancy, and the inventory APIs report which resources consume each licence. This gives finance and operations teams a single view of seat consumption that can be reconciled against vendor contracts.

Create a licence configuration for 'Microsoft SQL Server Enterprise' with 16 cores and ALLOWED_TENANCY_DEDICATED_HOST

Cross-Account Licence Sharing

Share centrally purchased licences with other accounts in an organisation through grants. The /CreateGrant and /AcceptGrant endpoints turn an owned licence into a delegated entitlement that another account can check out. This avoids duplicating licence configurations per account and centralises billing in one master account.

Create a grant for licence arn:aws:license-manager::123:license/abc with principal arn:aws:iam::456:root and allowed operation CheckoutLicense

Licence Audit Reporting

Generate scheduled reports that combine licence configuration usage and resource inventory for compliance reviews. The /CreateLicenseManagerReportGenerator endpoint accepts an S3 destination and frequency, after which License Manager publishes JSON or CSV reports that auditors can ingest directly. This replaces ad hoc spreadsheet collection with a repeatable pipeline.

Create a daily license report generator named 'all-licences' writing JSON to bucket 'compliance-reports' with prefix 'license-manager/'

AI Agent Licence Operations

AI agents call License Manager through Jentic to provision new licence configurations, issue grants when teams onboard new accounts, and answer compliance questions about current usage. Through Jentic, the agent searches by intent, loads the operation schema, and executes with credentials in your Jentic One instance. SigV4 signing happens inside Jentic so AWS keys never enter the agent runtime.

Search Jentic for 'list license configurations', load the ListLicenseConfigurations schema, and execute with no filters

Key Endpoints

50 endpoints — jentic publishes the only available openapi specification for aws license manager, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AWSLicenseManager.CreateLicenseConfiguration

Create a licence configuration

POST

/#X-Amz-Target=AWSLicenseManager.CreateLicense

Issue a new licence

POST

/#X-Amz-Target=AWSLicenseManager.CheckoutLicense

Check out a licence

POST

/#X-Amz-Target=AWSLicenseManager.CheckInLicense

Check a licence back in

POST

/#X-Amz-Target=AWSLicenseManager.CreateGrant

Create a grant for cross-account sharing

POST

/#X-Amz-Target=AWSLicenseManager.AcceptGrant

Accept a grant from another account

POST

/#X-Amz-Target=AWSLicenseManager.CreateLicenseConfiguration

Create a licence configuration

POST

/#X-Amz-Target=AWSLicenseManager.CreateLicense

Issue a new licence

POST

/#X-Amz-Target=AWSLicenseManager.CheckoutLicense

Check out a licence

POST

/#X-Amz-Target=AWSLicenseManager.CheckInLicense

Check a licence back in

POST

/#X-Amz-Target=AWSLicenseManager.CreateGrant

Create a grant for cross-account sharing

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AWS access key and secret for License Manager are stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list aws license configurations and usage' or 'share a licence with another account', and Jentic returns the matching License Manager operation with its input schema so the agent calls the right endpoint without reading the AWS reference.

Time to first call

FAQs

Specific to using AWS License Manager API through Jentic.

Why is there no official OpenAPI spec for AWS License Manager?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS License Manager via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the AWS License Manager API use?

License Manager uses AWS Signature Version 4 (SigV4) HMAC request signing scoped to the license-manager IAM service. Through Jentic, credentials sit in the encrypted vault and signing happens at execution time so the agent never sees the raw secret.

Can I track BYOL software with the License Manager API?

Yes. CreateLicenseConfiguration defines rules such as core counts, tenancy, and licence affinity, and the inventory APIs associate covered EC2 instances, RDS instances, and on-premises hosts with each configuration so usage is tracked centrally.

How do I share a licence with another AWS account through Jentic?

Search Jentic for 'create license grant', load the CreateGrant schema, submit the licence ARN, principal ARN, and allowed operations, and Jentic will sign and execute the call. The receiving account then accepts the grant via AcceptGrant.

What are the rate limits for the AWS License Manager API?

Per-region quotas apply, including default caps on licence configurations and grants per account and TPS limits on control plane operations such as CheckoutLicense. Check the License Manager service quotas in the AWS console for current values.

Can License Manager generate scheduled compliance reports?

Yes. CreateLicenseManagerReportGenerator schedules recurring reports that publish JSON or CSV to an S3 bucket. The report combines licence configuration usage with resource inventory, suitable for audit submission and finance reconciliation.

Can I check a licence in or out programmatically?

Yes. CheckoutLicense reserves an entitlement for a specified consumer with a digital signature, and CheckInLicense returns it. CheckoutBorrowLicense supports offline scenarios where the consumer keeps the entitlement for a fixed duration.

Can I limit what my agent is allowed to do with the AWS License Manager API?

Yes. Because Jentic One is self-hosted, you decide which License Manager operations your agent may call and which AWS credentials it uses. For read-only audit work you can allow only operations like ListLicenseConfigurations and GetLicenseUsage, while destructive calls such as DeleteLicenseConfiguration or CreateGrant stay out of reach unless you explicitly add them. The licence ARN and configuration travel in the request body of this X-Amz-Target RPC API, so scoping the operation set is how you constrain what the agent can do.

AWS License Manager

Connect the AWS License Manager to your agent

Capabilities

Start building with AWS License Manager API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs