Nutanix Prism Element

Storage and virtualisation

Renews the HTTPS certificate on one Prism Element cluster through the Nutanix REST API.

What happens

The appliance connects to Nutanix Prism Element through Nutanix v4.1 REST API on port 9440.
Select one Prism Element cluster through the v4.1 API in Prism Central or AOS 7.3+. The agent checks certificate, key and chain and sends a conditional update with an ETag.
Import restarts the interface gateway. The agent follows the task, reads back the certificate and checks the PE cluster’s TLS listener on 9440, rather than Prism Central’s own identity.

Connection: The package runs on the appliance, which connects over HTTPS to Nutanix v4.1 REST API, port 9440. No agent is installed.
Service ports: 9440
You need: Use an account with Cluster Admin, Prism Admin or Super Admin, or an IAM service account API key with such a role. Prism Admin or Super Admin also lets the agent follow the update task. Give the Prism Central address, or the cluster's own address on AOS 7.3 or later without Prism Central.
Platform: Prism Central pc.2025.2+ or AOS 7.3+, cluster management API v4.1
Actions: Discovery, Installation, Verification, Rollback
Packages: nutanix-prism-api 1.0.0
Note: Restoration and rollback need the previous matching certificate and key, which Nutanix does not return. An unfinished task or unanswered write is not blindly repeated or restored; run verify. Later certificate changes are preserved. Prism Central’s own certificate is outside this integration.

sslbrain offers: RSA 2048/4096, ECDSA P-256/P-384. Supply the certificate as PEM with a matching unencrypted key.

The chain should include intermediates and root, issuer first and root last. The cluster FQDN should appear in DNS SAN.