autorep from an EC2 instance of AutoSys client installation gives:
[03/20/2024 11:02:45] CAUAJM_E_10527 Timed out waiting for response from the AutoSys Application Server: [AEServerProd.example.com:9004]
[03/20/2024 11:03:45] CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10062 Failed to get initial configuration from AutoSys Application Server(s).
Architecture:
Below messages are seen in the AutoSys server log, $AUTOUSER/out/as_server.ACE for the above operation attempt
[03/20/2024 11:02:45] CAUAJM_I_30030 Client [AutoSys AutoRep:5615][16][ip-XX-XX-XX-XX.ec2.internal:50042:YY.YY.YY.YY] [-j %abcd%] session established.
[03/20/2024 11:02:45] CAUAJM_E_50007 Hostname [ip-XX-XX-XX-XX.ec2.internal] is invalid or unreachable over the network.
[03/20/2024 11:02:45] CAUAJM_E_30035 Client [AutoSys AutoRep:5615][16][ip-XX-XX-XX-XX.ec2.internal:50042:YY.YY.YY.YY] is not reachable. Session aborting...
[03/20/2024 11:02:45] CAUAJM_I_30033 Client [AutoSys AutoRep:5615][16][ip-XX-XX-XX-XX.ec2.internal:50042:YY.YY.YY.YY] session ended.
All the necessary ports were open correctly between the Client and the Server.
AutoSys Workload Automation
AutoSys Client from the Client node passes the real hostname of the Client, ip-XX-XX-XX-XX.ec2.internal, to the AutoSys server to do a name lookup against.
This real hostname of the AutoSys client is not resolvable from the Autosys Server side. It is only known to the AutoSys server as: AEClient.Example.com
ManagerHostAlias=AEClient.Example.com
CAUAJM_I_30030 Client [AutoSys AutoRep:5615][16][AEClient.Example.com:50042:YY.YY.YY.YY] [-j %abcd%] session established.
Additional information about the option is documented here: managerhostalias
Ports to be opened: AWS or Azure ports