We are pleased to announce the release of IBM Aspera Transfer Cluster Manager 1.2.4 for AWS and IBM Cloud. This release enhances status and error reporting, automates the configuration of cluster nodes, and expands the transfer management capabilities available via the Node API.
KEY NEW FEATURES
- Status update and pool management actions are now decoupled from auto-scale actions, which allows cluster state to be properly reflected in API calls and the ATC Manager UI even when auto-scaling is disabled.
- Improved error reporting for auto-scaling activity, including failures to launch new nodes due to start-frequency limits.
- Improved reporting of service stops and starts, including the logging of error messages if the action fails.
- The version of Aspera Enterprise Server that is used on cluster nodes is now reported by the nodes on startup and can be retrieved in the ATC Manager UI or using the API.
- In the rare cases when a new cluster node is launched but not registered with the ATC manager, nodes now detect this and automatically register.
- A new API call, /replace-nodes, replaces all nodes of a running cluster with new instances.
- Cluster nodes can now obtain configuration from any other cluster node or cluster manager upon startup.
- Enhancements to the Node API enable pausing, resuming, and cancelling Aspera Transfer Cluster Manager transfers from the Aspera Console UI.
- Cluster node AWS images are now enabled with enhanced networking using an elastic network adapter (ENA).
- The Softlayer DNS Service is now supported.