Autosys migration to AWS Cloud

Document ID : KB000096271
Last Modified Date : 16/05/2018
Show Technical Document Details
Question:
We are planning to migrate our Autosys environment (R11.3.6 SP1/SP6) to AWS Cloud environment. This is our current version: So, these are the questions of our migration plan and need your help answering these queries.
1. Can the Primary and Shadow schedulers run in different availability zones?
2. How many third machine(s) required to act as tie-breaker between Primary and Scheduler servers? And in which availability zone(s) they should run?
3. Currently Autosys database running on Oracle. We might use AWS Postgres SQL when we move to the cloud. Does Autosys R11.3.6 supports Postgres SQL?
4. Do you have a procedure to migrate Autosys database from Oracle to Postgres SQL?
5. Currently we have autosys agents services run using 'root' or Admin accounts. Is it possible to run them using non-root account?
6. The "machine_name: " in JIL file can be a load-balancer in AWS? Can we register these load balancer as machines in Autosys database? The goal is the machine name should be transparent to the users.
7. In special attention required while we export and import the existing JILs?
8. Do we need additional license to create a new Autosys environments and Agents in AWS?
9. We will be running Autosys R11.3.6 SP7 on AWS. Is that supported in AWS?
10. Finally, do you have any document to follow for the migration to AWS Cloud?
Answer:
1. Can the Primary and Shadow schedulers run in different availability zones?
[Answer] Yes, as long as they share VPC or routing rules are in place across subnets. Recommend using internal AWS routing rather than via public.
2. How many third machine(s) required to act as tie-breaker between Primary and Scheduler servers? And in which availability zone(s) they should run?
[Answer] 1 TIE breaker which can be hosted on either AZ as long as VPC is setup appropriately.
3. Currently Autosys database running on Oracle. We might use AWS Postgres SQL when we move to the cloud. Does Autosys R11.3.6 supports Postgres SQL?
[Answer] No, we do not support Postgres for AE yet.
4. Do you have a procedure to migrate Autosys database from Oracle to Postgres SQL?
[Answer] Not currently supported.
5. Currently we have autosys agents services run using 'root' or Admin accounts. Is it possible to run them using non-root account?
[Answer] Yes, but they must have access to all which is required to process your jobs – and root has this by default.
6. The "machine_name: " in JIL file can be a load-balancer in AWS? Can we register these load balancer as machines in Autosys database? The goal is the machine name should be transparent to the users.
[Answer] Yes. Yes.
7. In special attention required while we export and import the existing JILs?
[Answer] What is the source and target versions of AE? No special requirements should be necessary.
8. Do we need additional license to create a new Autosys environments and Agents in AWS?
Answer] This will need to be answered by their Account Team
9. We will be running Autosys R11.3.6 SP7 on AWS. Is that supported in AWS?
[Answer] Yes
10. Finally, do you have any document to follow for the migration to AWS Cloud?
[Answer] Not currently.