Integrations
Certificates deployed where you already run
LapseZero issues certificates from Let's Encrypt, renews them before they expire, and deploys them to your servers and cloud products automatically. It works with 9 DNS providers, 36 deployment targets and 7 notification channels.
DNS providers (9)
Connect your DNS provider and LapseZero handles domain validation for you. With Alibaba Cloud, Tencent Cloud, Huawei Cloud, Volcengine, AWS, Google Cloud and Azure, the same credentials also deploy to their cloud products.
DNS hosted somewhere else? Add one CNAME record instead. It works with any DNS host and needs no DNS credentials. See DNS delegation.
| Provider | Used for | Credentials |
|---|---|---|
| DNS + Cloud deployment | AccessKey ID / AccessKey Secret | |
| DNS + Cloud deployment | SecretId / SecretKey | |
| DNS | API Token | |
| DNS + Cloud deployment | Access Key ID / Secret Access Key | |
| DNS + Cloud deployment | Access Key ID / Secret Access Key | |
| DNS | API Key / API Secret | |
| DNS + Cloud deployment | Access Key ID / Secret Access Key | |
| DNS + Cloud deployment | Service Account JSON Key | |
| DNS + Cloud deployment | Tenant ID / Client ID / Client Secret |
Deployment targets (36)
After every issuance and renewal, LapseZero delivers the new certificate to your selected servers, cloud resources or certificate stores.
Certificates you've already bought can be uploaded and deployed to the same targets, and each new one you upload is deployed automatically.
Cloud deployments only need least-privilege access: when you add cloud credentials, the console lists the permissions needed by your selected products.
| Target | What gets updated |
|---|---|
| SSH server | Certificate and key files at the paths you choose, written over SFTP. An optional command runs afterwards. |
| Alibaba Cloud CDN | The HTTPS certificate of a CDN domain. |
| Alibaba Cloud CLB (formerly SLB) | Uploaded as a CLB server certificate and set for this domain on an HTTPS listener. Certificates for other domains on the listener keep working. |
| Alibaba Cloud ALB | Uploaded to Certificate Management Service and set for this domain on an HTTPS listener. Certificates for other domains on the listener keep working. |
| Alibaba Cloud NLB | Uploaded to Certificate Management Service and set for this domain on a TCPSSL listener. Certificates for other domains on the listener keep working. |
| Alibaba Cloud DCDN | The HTTPS certificate of a DCDN domain. |
| Alibaba Cloud ESA | Updates the uploaded certificate for this domain on the ESA site in place, or adds one if there isn't any. Other certificates on the site are left untouched. |
| Alibaba Cloud WAF 3.0 | Uploaded to WAF and set as the certificate of a protected domain. |
| Alibaba Cloud OSS | The certificate of a custom domain bound to a bucket. |
| Alibaba Cloud Certificate Management Service | Automatically uploads certificates to the certificate store after issuance and renewal, ready to select in Alibaba Cloud products. |
| Tencent Cloud SSL Certificates | Automatically uploads certificates to the certificate store after issuance and renewal, ready to select in Tencent Cloud products. |
| Tencent Cloud CDN | Uploaded to Tencent Cloud SSL Certificates and set on a CDN domain. |
| Huawei Cloud SSL Certificate Manager | Automatically uploads certificates to the certificate store after issuance and renewal, ready to select in Huawei Cloud products. |
| Huawei Cloud CDN | Uploaded to Huawei Cloud SSL Certificate Manager and set on a CDN domain, keeping your existing HTTPS settings. |
| Huawei Cloud ELB | Uploaded to Huawei Cloud ELB and set for this domain on an HTTPS listener. Certificates for other domains on the same listener are left as they are. |
| Volcengine Certificate Center | Automatically uploads certificates to the certificate store after issuance and renewal, ready to select in Volcengine products. |
| Volcengine CDN | Uploaded to Volcengine Certificate Center and set on a CDN domain, keeping your existing HTTPS settings. |
| Volcengine ALB | Uploaded to Volcengine Certificate Center and set for this domain on an HTTPS listener. Certificates for other domains on the same listener are left as they are. |
| Volcengine CLB | Uploaded to Volcengine Certificate Center and set for this domain on an HTTPS listener. Certificates for other domains on the same listener are left as they are. |
| Qiniu CDN | Uploads the certificate and replaces it on your CDN domain, keeping your existing HTTPS settings. |
| Upyun CDN | Uploads the certificate and replaces it on your CDN domain, keeping your existing HTTPS settings. |
| Tencent Cloud COS | Uploaded to Tencent Cloud SSL Certificates and set on a bucket's custom origin domain. |
| Tencent Cloud CLB | Uploaded to Tencent Cloud SSL Certificates and set for this domain on an HTTPS listener. Certificates for other domains on the listener keep working. |
| Tencent Cloud EdgeOne | Uploaded to Tencent Cloud SSL Certificates and set on an EdgeOne domain. |
| Tencent Cloud WAF (SaaS) | Uploaded to Tencent Cloud SSL Certificates and set on a WAF protected domain. |
| Amazon CloudFront | Imported into ACM in us-east-1 and set as the certificate the CloudFront distribution serves. Your TLS security policy stays as it is. The certificate must cover every domain name on the distribution. |
| AWS Application Load Balancer | Imported into ACM in the listener's region and set for this domain on an HTTPS listener. Certificates for other domains on the listener keep working. |
| AWS Network Load Balancer | Imported into ACM in the listener's region and set for this domain on a TLS listener. Certificates for other domains on the listener keep working. |
| Amazon API Gateway | Imported into ACM (us-east-1 for edge-optimized REST APIs, otherwise the API's region) and set on the custom domain name. Custom domains with mutual TLS are not supported yet. |
| AWS Certificate Manager (update an imported certificate) | Updates a certificate you imported into ACM, so every AWS service using it, such as a Classic Load Balancer or Elastic Beanstalk, switches to the new certificate without changes on your side. Only certificates you imported yourself with an RSA 2048 key are supported. |
| AWS Amplify Hosting | Imported into ACM in us-east-1 and set as the certificate of an Amplify custom domain. The certificate must cover all of the domain's subdomains. From then on LapseZero renews it instead of Amplify. |
| Google Cloud Certificate Manager (update a self-managed certificate) | Updates an existing self-managed certificate while keeping its resource name and bindings. The new and existing certificates must contain exactly the same domain names. Google-managed and legacy Classic Certificates are not supported. |
| Azure Key Vault (update an imported certificate) | Imports a new version of a certificate you imported into Key Vault, so Azure services that reference it without a pinned version, such as Application Gateway and Front Door, switch to the new certificate. Certificates generated in Key Vault are not supported. |
| Windows IIS | The certificate on a dedicated SNI HTTPS binding in IIS on Windows Server 2016, 2019, 2022 and 2025, updated without restarting the site. |
| 1Panel websites | The certificate in 1Panel used by your websites, updated through 1Panel's API on the server. 1Panel applies it to every website using that certificate and reloads. |
| Nginx Proxy Manager | A Custom Certificate you uploaded to the official Docker NPM, updated in place. Website bindings stay as they are. |
Nginx, Apache, BT Panel and 1Panel sites
- Install the deployment agent with one command, then choose Discover sites in the console. It lists the HTTPS sites in Nginx (including BT Panel sites), Apache and 1Panel. Tick the ones to take over.
- Nginx, Apache and BT Panel sites: new certificates are written back to the files the site already uses, then Nginx or Apache is reloaded. Your site configuration stays as it is. Apache 2.4 is supported on mainstream Linux distributions.
- 1Panel websites: add a 1Panel API key once and certificates are updated through 1Panel itself, so 1Panel shows the new certificate and saving website settings later won't bring back the old one.
- The agent connects out to LapseZero to fetch its jobs. No inbound port to open, and no SSH login to hand over. Prefer not to install it? Nginx, Apache and BT Panel sites can also be deployed over SSH, as described below.
- If a deployment fails, the original certificate is restored and your site keeps serving it. You are notified either way.
SSH deployment
- Sign in with a password or private key. The connection is tested when you save the host.
- Ready-made file layouts for Nginx, Apache, HAProxy and Tomcat (PKCS#12), written over SFTP to the paths you choose.
- Files are updated in place, so ownership and symlinks stay as they are. An optional command such as a reload runs once all files are written.
- If a write or the command fails, the original files are restored automatically and your server keeps serving the current certificate. You are notified either way.
Notification channels (7)
Get notified where your team already works when a certificate is issued, deployed or about to expire, or when something needs your attention. Each channel picks the events it receives.
Certificate authority
- Certificates are issued by Let's Encrypt, trusted by all major browsers, with an RSA 2048 key generated for you. No CSR needed.
- Need a copy for somewhere else? Download the certificate and key in Nginx, Apache, Tomcat, IIS (PFX) or HAProxy format.