Overview
Polystack Key Manager supports two certificate workflows: storing externally issued certificates from your existing CA, and ordering certificates through a configured CA plugin for automated issuance. Both workflows produce a certificate container that can be consumed by the Load Balancer service for HTTPS termination.Prerequisites
- An active Polystack account with appropriate permissions
- Access to the Polystack Dashboard or CLI configured with credentials
- API credentials sourced (
source openrc.sh)
Store an Existing Certificate
Use this workflow when you have an externally issued certificate (Let’s Encrypt, DigiCert, your enterprise CA, etc.) and want to store it in Key Manager.1
Store the certificate secret
Store the X.509 certificate
2
Store the private key secret
Store the private key
3
Store the CA chain (recommended)
Store CA chain
4
Create a certificate container
Bundle into certificate container
Container is ready to reference in Load Balancer HTTPS listener configuration.
Order a Certificate
Certificate orders automate issuance through a Certificate Authority plugin configured by your administrator.- Create an order
- List and manage orders
Create a certificate order
Check order status
ACTIVE, retrieve the issued certificate container:Get the issued certificate container
Certificate order availability depends on your platform’s CA plugin configuration.
Contact your administrator to verify which CA backends are enabled.
Certificate Lifecycle Management
Verify a Certificate
Retrieve certificate and check expiry
Verify certificate matches private key
If both
md5sum values match, the certificate and private key are a valid pair.Next Steps
Containers
Bundle certificates into containers for Load Balancer use
ACL
Control which users and services can access certificate secrets
Store Secrets
Store other secret types alongside certificates
Troubleshooting
Resolve certificate container and order issues
