When setting up a high-availability (HA) Automation Suite deployment in an offline environment, which consideration is most critical for maintaining operational parity with an online deployment?
A.
Integrating with a public time synchronization (NTP) service to ensure event log consistency across nodes.
B.
Leveraging a cloud-based container auto-scaling service to maintain optimal bot distribution across nodes.
C.
Provisioning a fully internalized service mesh with locally hosted certificate authority (CA) for secure inter-service communication and service discovery.
D.
Connecting worker nodes to a centralized public telemetry aggregator to monitor performance and provide dynamic scaling suggestions.
In an offline or air-gapped environment, the Automation Suite cluster cannot contact public clouds, external certificate authorities, or remote services. To maintain operational parity, high availability, and end-to-end security, the cluster relies on an internal service mesh (powered by Istio) configured alongside a locally hosted Certificate Authority (CA). This internal architecture handles mutual TLS (mTLS), internal routing, service discovery, and traffic management between microservices without external dependencies. Online deployments often rely on external trust anchors or cloud-native providers, whereas an air-gapped cluster must manage internal certificate issuance and trust stores locally. Without an internalized service mesh and local CA, inter-service authentication fails in an isolated network. (Reference: UiPath Automation Suite Security Architecture – Offline Service Mesh and CA Configuration).
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit