AC Hosting Environment

AC Hosting Environment Documentation
  • 1 Release Notes
    • 1.1 End-Of-Life (EOL) Notice
    • 1.2 Support Policy
    • 1.3 Differences to CentOS
  • 2 Deployment
    • 2.1 Prerequisites
    • 2.2 Preparing to Install
    • 2.3 Installation
    • 2.4 Post Installation Steps
  • 3 AC Tools
    • 3.1 AC Configure Syslog
      • 3.1.1 Introduction
      • 3.1.2 Un/Installation
      • 3.1.3 Usage
    • 3.2 AC Firewall
      • 3.2.1 Introduction
      • 3.2.2 Un/Installation
      • 3.2.3 Usage
    • 3.3 AC Integrity
      • 3.3.1 Introduction
      • 3.3.2 Un/Installation
      • 3.3.3 Usage
      • 3.3.4 Integration Tips
    • 3.4 Make Bash Installer
      • 3.4.1 Introduction
      • 3.4.2 Un/Installation
      • 3.4.3 Usage
    • 3.5 AC X509 Authority
      • 3.5.1 Introduction
      • 3.5.2 Un/Installation
      • 3.5.3 Command Reference
      • 3.5.4 Certificates For Beginners
      • 3.5.5 CA Management
      • 3.5.6 Server, Client, and User Certificate Management
      • 3.5.7 Reporting Commands
      • 3.5.8 Troubleshooting

2.1 Prerequisites

September 13th, 2025

In addition to meeting the minimum system requirements, care should be taken size the system appropriately for the intended use case.

Always refer to your software documentation for correct system sizing and resource allocation.

There are three basic classes of use case for an ACHE deployment which affect how the system is resourced. Prepare your hardware in advance.

2.1.1 Lightweight (non storage) appliance

  • Minimum system requirements
  • No removeable storage bays

This covers scenarios where the expected usage or traffic is low and workload is not dependant on storage IO performance. In this scenario, it may be possible to run with the minimum system requirements. An example may be an internal DNS server. Ultimately, this type of deployment should never be used for file storage or database applications.

Even a lightweight appliance can be mission critical. The primary single boot disk should be a hardware RAID1 device to ensure resiliency.

2.1.2 SOHO Web server, Storage or Database applications

  • Exceeds system requirements
  • Multiple removable storage bays

These use cases reply on storage IO performance and storage expandability. In addition, the compute resources required for running the installed application server or database may be high.

Removable drive bays are mandatory for this class of use case.

2.1.3 Enterprise Web server (no local storage or database)

  • Exceeds system requirements
  • No removeable storage bays

We servers present a special case. The compute resources required by the application server may be high. However, file storage and database access is expected to be provided by an external dedicated host.

previous: Differences to CentOS next: Preparing to Install