Technical Solution
Technical Solution
Breadcrumbs

IaaS/PaaS Mode: Infrastructure Requirements and Recommendations

Anjana Data provides several installation kits:

  • 🆕 Interactive installer based on a Java service that guides you through the installation via a graphical interface.

  • Ansible deployment kit that facilitates the implementation of the solution by automating, step by step, the installation and startup of each microservice that makes up Anjana Data Platform. ⚠️ Discontinued (End of support Q4 2026)

  • Helm kit for container-based deployments on K8S.

Technical and Deployment Requirements

Supported Operating Systems and Technologies

  • Operating Systems: Ubuntu, RedHat.

  • Relational Databases: PostgreSQL, AWS RDS/Aurora PostgreSQL, AzureDB for PostgreSQL, GCP Cloud SQL for PostgreSQL, Embedded in VM.

  • S3 Storage: AWS S3, MinIO.

  • Indexer: SolR.

  • Other components: Ansible, Python, Zookeeper.

Note: Full details about the supported versions are available in the Ansible documentation and in the Kubernetes documentation.

Deployment Requirements

  • User with SSH access and root permissions on all provisioned machines and managed services.

  • Required connectivity to:

    • https://releases.anjanadata.com for downloading the installer, artifacts, and software packages.

    • https://veltesta.anjanadata.com for license activation and validation.

    • Between the nodes and the managed RDS and S3 services, if applicable.

    • Between all provisioned nodes in Standard and Balanced architectures, via SSH.

    • From Anjana nodes (Zeus) to/from the identity management systems. See Authentication documentation.

    • Software download from the operating system repositories (see list in the Ansible kits documentation).

  • Post-deployment access to portals:

    • 443 → /login, /configpanel, /swagger/swagger-ui.html

    • 9001 (Minio)

    • 8983 (SolR)

    • 9999 (Horus)

  • In the case of a managed database: there must be a database called anjana and a user with creation permissions.

  • In the case of managed S3: there must be 7 buckets (CDN, DSA, IMPORTS, TEXTAREA, WORKFLOWS, ANJANABACKUPS, ANJANALOGS).

  • Deployment is performed using an Ansible kit run from a central node.

  • The machine running the Ansible kit must have a fixed outbound IP address to the Internet.

  • Required architecture: x86_64 (Intel/AMD 64-bit).

  • Disk space: everything mounted on the root directory, using /opt and /tmp.

In SaaS Hybrid mode, the specific connectivity of the plugins machine (ports 15001+ to the governed data systems and the Tot module) is detailed in SaaS Hybrid Mode: Infrastructure Requirements and Recommendations.

Anjana Data provides different recommended configurations based on (but not identical to) the SaaS environment types Test, Base, Standard, and Balanced, which allow the deployment to be adapted to different volumes of users and data.

These architectures are designed to ensure:

  • Proper load distribution.

  • Scalability and redundancy according to the criticality of the environment.

  • Integration with managed database and S3 storage services.

NOTE: all disk sizes indicated below include the space required for the installation of system packages, handling of temporary files, installation directories, etc…

For the system to function correctly, the total space cannot be dedicated to the installation folder. E.g.: /opt

Test-type Infrastructure (POCs)

  • 1 VM - 8 VCore | 32 Gb RAM | 64Gb SSD

Base-type Infrastructure

  • 1 VM - 8 VCore | 32 Gb RAM | 64Gb SSD

  • Managed S3 - 64 Gb

Standard-type Infrastructure

  • 1VM (Core) - 4VCore | 20 Gb RAM | 64 Gb SSD

  • 1VM (Plugins) - 2VCore | 8Gb RAM | 32 Gb SSD

  • 1VM (Indexer) 2VCore | 4Gb RAM | 32 Gb SSD

  • Managed S3 - 128 Gb

  • Managed RDB - 2VCore | 2Gb RAM | 50Gb SSD

  • Managed MongoDB - 1VCore | 2Gb RAM | 16Gb SSD (self-managed if there is no cloud equivalent)

  • Managed RabbitMQ - 1VCore | 1Gb RAM | 16Gb SSD (self-managed if there is no cloud equivalent)

  • Managed Valkey - 1VCore | 512Mb RAM (self-managed if there is no cloud equivalent)

Note: Requirements for the Ansible kit or Installer binary in case it is deployed on a separate VM, with minimum requirements of 2vCPU | 2GB RAM | 32GB SSD

Balanced-type Infrastructure

  • 2VM (FrontBack) - 4VCore | 20 Gb RAM | 64 Gb SSD

  • 1VM (Plugins) - 2VCore | 8Gb RAM | 32 Gb SSD

  • 3VM (Indexer) - 2VCore | 4Gb RAM | 32 Gb SSD

  • Managed S3 HA - 128 Gb

  • Managed RDB HA - 4VCore | 4Gb RAM | 50Gb SSD

  • Managed MongoDB - 1VCore | 2Gb RAM | 16Gb SSD (self-managed if there is no cloud equivalent)

  • Managed RabbitMQ - 1VCore | 1Gb RAM | 16Gb SSD (self-managed if there is no cloud equivalent)

  • Managed Valkey - 1VCore | 512Mb RAM (self-managed if there is no cloud equivalent)

Certificates

All connections between Anjana Data components are secured using SSL/TLS with certificates managed by the client. Full details on requirements, file naming conventions, and delivery procedures can be found in the official documentation: