Connecting to AWI, the JCP and REST Processes Using an Ingress or a Gateway API

Using a Kubernetes routing solution allows you to expose AWI, the REST and JCP endpoints, and the Install Operator service. You can achieve this using either a traditional Ingress or the Gateway API. By default, neither routing component is enabled (enabled: false) in the values.yaml file. For more information, see Preparing the Ingress and TLS/SSL Certificates and Preparing the Gateway API.

Reaching the JCP and REST Endpoints

External components such as TLS/SSL Agents, the TLS Gateway, the Automation.AI component, and the CallAPIs for Java and SAP need to connect to your AAKE cluster. Therefore, you must ensure that your chosen routing solution (Gateway API, Ingress, or HTTPS load balancer) is reachable and configured with the required certificates.

If you choose to use the Gateway API, external connections require your publicly assigned certificates, while the internal routing to the backend JCP and REST components uses self-signed certificates automatically provided by Automic Automation.

The value assigned to the JCP_ENDPOINT parameter represents the address the Agent uses to connect to the JCP. The Gateway API, Ingress, or load balancer simply makes this JCP address reachable from outside the cluster. The endpoint is also the value defined in the connection= parameter on the [TCP/IP] section of the INI file of the respective TLS/SSL Agent and/or TLS Gateway.

More information:

• Types of Server Processes

• TLS/SSL Considerations for Automic Automation

• Securing Connections to the AE (TLS/SSL)

• JCP_ENDPOINT

• REST_ENDPOINT

• Agents INI Files

• TLS Gateway INI file

• CallAPI Overview

• Automic Automation's Generative AI Capabilities

Reaching the Automic Web Interface

The Automic Web Interface uses TLS/SSL and WebSockets to secure the communication between the AWI browser and the web server within the cluster. Therefore, you have to make sure that the Gateway API / ingress / HTTPS load balancer to which the AWI browser connects is reachable and that the required certificates are in place.

Important! Be aware that the AWI Gateway API / ingress / HTTPS load balancer must support sticky sessions. For more information, see Setting Up the Load Balancer and Configure Proxies.

The specific configuration of your load balancer depends on the cloud provider services you use. For detailed information, please refer to the respective official documentation.

See also:

• Preparing for the Container-Based Installation
• Installing and Migrating Container-Based Systems
• Configuring Container-Based Systems
• Installing and Configuring Agents for Container-Based Systems