This is most likely a communication configuration issue. The product itself does not work any differently in AWS than it does on premise. In fact, unless you're using AWS RDS for the database, the product has no idea it's even running in AWS.
I can't tell by the description whether the CLI problem is being performed from a client machine or on the AutoSys server machine. If the problem occurs from a client machine, try executing a CLI like autorep on the app server machine. If the CLI works on the app server machine, then the problem is due to communication problems (e.g. SSA configuration, port routing, firewall blocking ports, etc.) Common problems seen with firewalls is blocking the SSA port (7163 default) in one direction or the other between client and app server machines. You may need to enable firewall IP logging to diagnose point of failure.
Focus on one problem at a time (e.g. CLI). Most likely all problems are related and apply to different ports.
Original Message:
Sent: 10-21-2019 03:23 PM
From: Patricia Williams
Subject: Workload Automation Migration
Our admin has just migrated Autosys to AWS. At this point we are not able to autoping, auto_chk, autosyslog or anything else. All the services appear to be running. The webportal will not open. I've gone down several paths for troubleshooting. The one change that was made was the IP of the AE and WCC did change.
Autosys Version: 11.3.5
Windows: Win2008