Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

3.8 KB
Raw Blame
---
title: "External CA"
sidebarTitle: "Overview"
description: "Connect external Certificate Authorities to Infisical."
---

Integrate with External Certificate Authorities (CAs) to use existing PKI infrastructure or connect to public CAs for certificate issuance.

<Info>
  This page is for product admins setting up PKI infrastructure. Teams issuing certificates should see [Applications](/documentation/platform/pki/applications/overview).
</Info>

## Public CAs

Public CAs issue certificates that browsers trust, for public-facing services:

<CardGroup cols={2}>
  <Card title="ACME-compatible CA" icon="bot" href="/documentation/platform/pki/ca/acme-ca">
    Connect to any CA that supports ACME, such as ZeroSSL or Buypass.
  </Card>
  <Card title="Let's Encrypt" icon="lock" href="/documentation/platform/pki/ca/lets-encrypt">
    Free, automated certificates for public domains.
  </Card>
  <Card title="DigiCert (ACME)" icon="shield-check" href="/documentation/platform/pki/ca/digicert">
    DigiCert certificates through ACME with External Account Binding.
  </Card>
  <Card title="DigiCert (CertCentral API)" icon="shield-half" href="/documentation/platform/pki/ca/digicert-direct">
    DigiCert TLS and code signing certificates through the CertCentral Services API.
  </Card>
  <Card title="GoDaddy" icon="globe" href="/documentation/platform/pki/ca/godaddy">
    Domain Validated certificates through the GoDaddy Certificates API.
  </Card>
  <Card title="Sectigo" icon="award" href="/documentation/platform/pki/ca/sectigo">
    Sectigo certificates through ACME with External Account Binding.
  </Card>
  <Card title="AWS ACM public CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-acm-public-ca">
    Publicly trusted certificates from AWS Certificate Manager.
  </Card>
</CardGroup>

## Private CAs

Private CAs issue certificates for internal services, from PKI you already run in the cloud or on premises:

<CardGroup cols={2}>
  <Card title="Microsoft ADCS" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/adcs">
    Microsoft AD CS over MS-WCCE through an Infisical Gateway.
  </Card>
  <Card title="Azure ADCS (web enrollment)" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/azure-adcs">
    Microsoft AD CS over HTTPS web enrollment.
  </Card>
  <Card title="AWS private CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-pca">
    Private certificates from AWS Private Certificate Authority.
  </Card>
  <Card title="Venafi TLS Protect Cloud" icon="cloud" href="/documentation/platform/pki/ca/venafi">
    Venafi's cloud-based certificate management platform.
  </Card>
  <Card title="Venafi TPP" icon="server" href="/documentation/platform/pki/ca/venafi-tpp">
    Venafi Trust Protection Platform, on premises.
  </Card>
</CardGroup>

<Note>
  Don't see your CA? Contact [email protected] and we'll help you set up the integration.
</Note>

## FAQ

<AccordionGroup>
  <Accordion title="Can I use both Internal CAs and External CAs together?">
    Yes. You can have both Internal and External CAs in Infisical Certificate Management.
  </Accordion>
</AccordionGroup>

## What's next?

<CardGroup cols={2}>
  <Card title="Internal CA" icon="landmark" href="/documentation/platform/pki/ca/private-ca">
    Create your own private CA hierarchy.
  </Card>
  <Card title="Certificate Policies" icon="file-text" href="/documentation/platform/pki/settings/policies">
    Define constraints for certificates.
  </Card>
  <Card title="Certificate Profiles" icon="file-badge" href="/documentation/platform/pki/settings/profiles">
    Create profiles that link CAs with policies.
  </Card>
  <Card title="Applications" icon="layout-grid" href="/documentation/platform/pki/applications/overview">
    Issue certificates through Applications.
  </Card>
</CardGroup>