Setting up Orchestrator in the Cloud

The following are the setup options for Orchestrator in the cloud (assuming high availability installation):

  • No shared storage, because typically there is no file-based storage available (only object storage).
  • An external database with an high availability solution of its own is accessed with a unique virtual IP address.
  • The file trigger history is stored in the external database.
  • Plugins are not shared by the nodes, so importing and archiving a plugin must be done on both nodes of the cluster.
  • Edits to the Ochestrator configuration and Apache configuration must be done on both nodes of the cluster.
Note: ACM (Aspera Cluster Manager) is not an option for cloud installation, so the services must be started and controlled by the operating system.