Installation

This documentation covers the technical and architectural requirements needed to deploy the Anjana Data platform and/or its plugins on client infrastructures, whether in IaaS, PaaS, SaaS Hybrid or OnPremise environments.

The objective is to provide a clear and structured guide on:

• Operating systems, databases and supported technologies.

• Conditions and prerequisites for deployment.

• Software map and main components.

• Required connectivity between nodes and external services.

• Recommended architectures according to the type of environment.

In this way, the client's infrastructure and operations teams will be able to properly prepare their environments before starting the installation, ensuring a successful deployment aligned with Anjana Data's best practices.

Deployment Prerequisites

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 Persistence: AWS S3, MinIO

• Indexer: SolR

• Other components: Ansible, Python, Zookeeper

Deployment Requirements

• User with SSH access and root permissions on all provisioned managed machines and 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 nodes with managed RDS and S3 services, if applicable.

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

  • In SaaS Hybrid mode, from the plugin nodes (ports 15001+) to the governed data systems and to the Tot module. See TOT Plugins documentation.

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

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

• Post-deployment portal access:

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

  • 9001 (Minio)

  • 8983 (SolR)

  • 9999 (Horus)

• In case of managed DB: a database named anjana must exist along with a user with creation permissions.

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

• Deployment is carried out via an Ansible kit executed 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 in the root directory, using /opt and /tmp.

Software Map

The Anjana Data platform is organized into different functional zones, each composed of specialized modules that cover the complete data governance and artificial intelligence experience. In the General Description you will find a detailed explanation of each module (features, technologies and use cases).

Connection Architecture

The Anjana Data architecture is designed to govern different technologies, clusters and environments in an agnostic and flexible manner, allowing deployment in complex scenarios such as multi-cloud, hybrid, big data or on-premise environments, and offering the ability to evolve alongside new technologies.

Thanks to its modular design based on Spring Cloud and microservices, Anjana Data Platform ensures:

• Independence from third-party product versions.

• High availability and practically unlimited horizontal scalability.

• Deployments adaptable to both cloud-managed environments and on-premise infrastructures.

• Interoperability and extensibility through APIs and connectors/plugins.

For a complete description of the technical and functional architecture, consult the official General description documentation.

Recommended Architectures

Anjana Data provides different recommended configurations for environments that allow the deployment to be adapted to different volumes of users and data.

These architectures are designed to ensure:

• Correct load distribution.

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

• Integration with managed DB and S3 storage services.

All details about the recommended architectures can be found in the Deployment documentation.

Certificates

All connections between Anjana Data components are secured via SSL/TLS, so it is essential to have a wildcard certificate associated with the domain of each platform instance or of the plugins in case of hybrid SaaS deployments
(example: *.anjanadata.cliente.com or *.pluginsanjana.cliente.com).

For correct deployment, only the following files are required:

• fullchain.pem

• privatekey.pem

The complete details on how to generate, place and integrate the certificates can be found in the official documentation:

• 🔗 Deployment manual with Ansible kit – Environment setup

• 🔗 Certificate mechanics in Anjana Data