AWS CloudHSM V2

Name: AWS CloudHSM V2 API
Brand: AWS CloudHSM V2
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets Managementhmac15 EndpointsREST

Install Jentic One Beta

Connect the AWS CloudHSM V2 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS CloudHSM V2, 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 CloudHSM V2 API.

Create CloudHSM clusters in a target VPC and initialize them with a customer trust anchor

Add or delete individual HSM appliances within a cluster to scale cryptographic capacity

Take, describe, and restore CloudHSM backups, including modifying backup retention

GET STARTED

Start building with AWS CloudHSM V2 API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and manage dedicated AWS CloudHSM clusters, individual HSMs, and encrypted backups for FIPS 140-2 Level 3 key custody. Backed by 15 cluster, HSM, and backup operations.

Use for: I need to create a CloudHSM cluster in a specific VPC, Provision an additional HSM in an existing CloudHSM cluster, List all CloudHSM backups for a cluster, Copy a CloudHSM backup to another region for disaster recovery

Not supported: Does not handle key generation or cryptographic operations on the wire, KMS multi-tenant keys, or TLS certificate issuance - use for CloudHSM cluster, HSM, and backup lifecycle management only.

Use Cases

Patterns agents use AWS CloudHSM V2 API for, with concrete tasks.

★ FIPS 140-2 Level 3 Key Custody for Regulated Workloads

Financial services, healthcare, and government workloads that must hold cryptographic keys in FIPS 140-2 Level 3 hardware can use CloudHSM V2 to provision dedicated HSM clusters inside a VPC. The API creates the cluster, attaches HSMs, and manages the backup lifecycle, so an agent can stand up compliant key storage without console clicks. Typical clusters use 2-3 HSMs across availability zones for high availability.

Create a CloudHSM cluster in subnets subnet-aaa and subnet-bbb, then add two HSMs to the cluster

Cross-Region Disaster Recovery for Cryptographic Material

Use CopyBackupToRegion to replicate a CloudHSM backup from a primary region to a secondary region so that a new cluster can be restored from it if the primary region becomes unavailable. The API supports listing backups, modifying retention attributes, and restoring backups marked for deletion within their retention window. This pattern is required by many DR runbooks for HSM-protected workloads.

Copy backup backup-1234 from us-east-1 to us-west-2 and verify the destination backup reaches READY state

Programmatic HSM Fleet Tagging and Inventory

Operations teams managing many CloudHSM clusters across accounts can use ListTags, TagResource, and UntagResource to enforce a tagging standard for cost allocation, ownership, and compliance scope. DescribeClusters and DescribeBackups expose cluster state and backup metadata so an agent can produce an up-to-date inventory of HSM resources and their lifecycle status.

List all CloudHSM clusters in the current account and tag any without a CostCenter tag with CostCenter=unassigned

AI Agent Integration via Jentic

Through Jentic, an AI agent uses the CloudHSM V2 API by searching for an intent like 'create a CloudHSM cluster', loading the schema for CreateCluster, and executing the call with VPC subnet IDs and HSM type. The agent never sees raw AWS access keys - Jentic signs the SigV4 request server-side using credentials stored in your Jentic One instance.

Search Jentic for 'create a CloudHSM cluster', load the CreateCluster schema, and execute it for HSM type hsm1.medium in the supplied subnet IDs

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for aws cloudhsm v2, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=BaldrApiService.CreateCluster

Create a CloudHSM cluster in a VPC

POST

/#X-Amz-Target=BaldrApiService.CreateHsm

Provision an HSM inside an existing cluster

POST

/#X-Amz-Target=BaldrApiService.InitializeCluster

Initialize a cluster with a signed trust anchor

POST

/#X-Amz-Target=BaldrApiService.DescribeClusters

List and describe CloudHSM clusters

POST

/#X-Amz-Target=BaldrApiService.DescribeBackups

List backups for clusters in the account

POST

/#X-Amz-Target=BaldrApiService.CopyBackupToRegion

Copy a backup to a second region for DR

POST

/#X-Amz-Target=BaldrApiService.RestoreBackup

Restore a backup pending deletion

POST

/#X-Amz-Target=BaldrApiService.DeleteCluster

Delete an empty CloudHSM cluster

POST

/#X-Amz-Target=BaldrApiService.CreateCluster

Create a CloudHSM cluster in a VPC

POST

/#X-Amz-Target=BaldrApiService.CreateHsm

Provision an HSM inside an existing cluster

POST

/#X-Amz-Target=BaldrApiService.InitializeCluster

Initialize a cluster with a signed trust anchor

POST

/#X-Amz-Target=BaldrApiService.DescribeClusters

List and describe CloudHSM clusters

POST

/#X-Amz-Target=BaldrApiService.DescribeBackups

List backups for clusters in the account

Why Jentic?

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

Credential isolation

Your AWS access key ID and secret access key are stored once, encrypted, by your own Jentic One instance, and the Signature Version 4 signature is computed at execution time. The raw keys never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a CloudHSM cluster' or 'copy an HSM backup to another region', and Jentic returns the matching CloudHSM V2 operation with its input schema so the agent calls the right action without crawling the AWS reference.

Time to first call

FAQs

Specific to using AWS CloudHSM V2 API through Jentic.

Why is there no official OpenAPI spec for AWS CloudHSM V2?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS CloudHSM V2 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 CloudHSM V2 API use?

CloudHSM V2 uses AWS Signature Version 4 (HMAC) signed requests with an IAM access key ID and secret key, plus a session token if using temporary credentials. Through Jentic, those credentials live in your Jentic One instance and the SigV4 signature is computed server-side, so the agent context never contains the raw secret.

Can I create and initialize a CloudHSM cluster with this API?

Yes. Call CreateCluster with a list of VPC subnet IDs and an HSM type, then call CreateHsm to add HSM appliances, and finally InitializeCluster with a signed certificate from your customer CA to bring the cluster to ACTIVE state.

How do I take and copy a CloudHSM backup across regions?

Backups are taken automatically on cluster changes. Use DescribeBackups to find the backup ID, then call CopyBackupToRegion with the destination region to replicate it. The destination backup gets a new BackupId you can later pass to a CreateCluster SourceBackupId in that region.

What are the rate limits for the AWS CloudHSM V2 API?

AWS CloudHSM V2 enforces standard AWS service throttling - most control-plane calls (CreateCluster, CreateHsm, DescribeBackups) are limited to a small number of TPS per account per region, and throttled responses return ThrottlingException. Use exponential backoff; the AWS SDKs that Jentic wraps already implement this.

How do I provision a CloudHSM cluster with an AI agent through Jentic?

Run pip install jentic, then have the agent search for 'create a CloudHSM cluster', load the CreateCluster schema, and execute it with the SubnetIds and HsmType parameters. Follow with CreateHsm for each HSM and DescribeClusters to poll for ACTIVE state.

Can I limit what my agent is allowed to do with the AWS CloudHSM V2 API?

Yes. Because you run Jentic One yourself, you decide which CloudHSM V2 operations your agent may call, so you can grant read-only actions like DescribeClusters and DescribeBackups while leaving out cluster and HSM creation. Since CloudHSM V2 passes cluster, HSM, and backup identifiers in the request body rather than the URL, scoping is done by operation: destructive calls such as DeleteCluster or RestoreBackup are excluded unless you explicitly add them. Your AWS access key stays in your own Jentic One instance and the request is signed at execution time, so the agent only ever exercises the operations you approve.

AWS CloudHSM V2

Connect the AWS CloudHSM V2 to your agent

Capabilities

Start building with AWS CloudHSM V2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs