Plan your topology and networking configuration

Install Ansible Automation Platform 2.6 using a tested deployment model. Choose between an enterprise reference architecture for high performance and scalability or a growth architecture for resource-constrained environments.

It is possible to install Ansible Automation Platform on different infrastructure reference architectures and with different environment configurations. Red Hat does not fully test architectures outside of published reference architectures. Red Hat recommends using a tested reference architecture for all new deployments and provides commercially reasonable support for deployments that meet minimum requirements.

The following diagram is a tested container enterprise architecture:

Figure 1. Reference architecture overview

Infrastructure reference architecture that Red Hat has tested that customers can use when self-managing Ansible Automation Platform

DNS, NTP, and service planning
Copy link

When installing Ansible Automation Platform, DNS and NTP configurations are crucial for a successful deployment and proper operation.

DNS
Copy link

Define a valid Fully Qualified Domain Name (FQDN) for all infrastructure nodes in your installation inventory file. Resolving these to a routable IP address in DNS passes installer checks and helps ensure a successful setup.

DNS and load balancing
Copy link

When using a load balancer with Ansible Automation Platform, an additional FQDN is required. For example, aap.example.com could be used for the load balancer to direct traffic to each platform gateway component defined in the installation inventory.