Apache

CertGuardian allows certificates to be installed automatically on Apache servers through the certificates.yaml configuration file.

This file is located inside the agent's config directory:

certguardian-agent/
├── certguardian-agent(.exe)
└── config/
    └── certificates.yaml

Configuration Example

The following example shows a certificate that will be installed in two different locations:

certificates:
  - id: 1
    installations:
      - id: web-frontend
        type: apache
        config:
          fullchain_path: /opt/apache/frontend/fullchain.pem
          key_path: /opt/apache/frontend/private.key
          reload: systemctl reload apache2

      - id: web-backend
        type: apache
        config:
          fullchain_path: /opt/apache/backend/fullchain.pem
          key_path: /opt/apache/backend/private.key
          reload: systemctl reload apache2

Configuration Structure

id

Certificate identifier within the CertGuardian platform.

id: 1

This identifier must match the certificate identifier configured in the platform.

installations

List of installations associated with the certificate.

A certificate can have one or more installations.

installations:

installation.id

Unique installation identifier.

id: web-frontend

This value is used to identify the installation within the configuration file.

installation.type

Installation type that will be executed by the agent.

For Apache installations, this value must be set to:

type: apache

installation.config

Contains the Apache-specific installation parameters.

config:

Apache Parameters

fullchain_path

Full path where the certificate (fullchain) will be installed.

fullchain_path: /opt/apache/frontend/fullchain.pem

key_path

Full path where the certificate private key will be installed.

key_path: /opt/apache/frontend/private.key

reload

Command executed by the agent once the installation has been completed.

This is typically used to reload the Apache configuration and apply the new certificate.

reload: systemctl reload apache2

Multiple Installations

A single certificate can be associated with multiple installations.

In the example above, the certificate will be deployed to two different locations:

• /opt/apache/frontend/
• /opt/apache/backend/

After each installation is completed, the agent will execute the command defined in the reload parameter.