What are the best practices, guidelines, and procedures for installing using Control-M in an Amazon Web Services AWS cloud? |
See attached Whitepaper for instructions on the procedures and guidelines for installing Control-M in AWS cloud =========================================== Additional information regarding Control-M AWS support Q: Is Control-M available on AWS Marketplace? BMC Software will offer "Control-M Application And Data Workflow Orchestration" to new subscribers on AWS Marketplace. As a current subscriber, your use and subscription to "Control-M - Application Workflow Orchestration" is unaffected; you can continue to create new instances, and any running instances will not be affected in any way. For standard installation on AWS please refer to the Installation guide. Q. What is the official support policy for Control-M in AWS cloud? Control-M deployment on AWS is available with the most currently supported releases on the following databases:
Q. What is the minimum Control-M version and Fix Pack level recommended on AWS Cloud platform? Control-M 9.0.18 and higher Q. Which installation media should be used to install on a Cloud platform? Control-M using the regular installation media from the BMC EPD site Q. Is Control-M 9.0.18 supported with Amazon Linux? Please see the SPAC (Supported Product Availability & Compatibility) below for current information. http://customerapps.bmc.com/spac/o/welcome.html Q: Which EC2 instance type should be used for Control-M? M5 is recommended. Avoid using T2 instance type whose default kernel setting in Linux is insufficient for Control-M. Recommended class is M5a. Q. Is there a pay-per-use license option for the vendors’ software for use on Public Cloud (AWS/Azure), where costs including support and updates can be paid on a per-use/capacity based model? Currently BMC does not provide “pay per use” or SaaS models. Please contact sales office for availability of these cofigurations Q. How to connect an Agent on AWS to Control-M/Server on-premise host across the internet? The on-premise Control-M/Server needs to be able to initiate a TCP/IP connection to the Control-M/Agent host (in AWS). The Control-M/Agent on AWS can not initiate a TCP/IP connection to Control-M/Server. The ideal solution for this scenario is using a Persistent connection where the Control-M/Server is connecting to the Control-M/Agent. The Control-M/Agent should have the parameter “Allow comm init” set to N. The only port that should be opened is the "Server to Agent" port on the Control-M/Agent host as inbound. Q. Can Control-M/Server in AWS be deployed in a stateless model (not bound to a particular IP address)? Is there any way to distribute workloads across multiple Control-M/Servers, just to have the simplest possible supported implementation whereby the Control-M/Server can move in AWS without the need to update a gateway definition. A. Stateless model is more for Webserver, it comes with scale up and scale down solutions. Control-M server will NOT work in such stateless model. Even if one utilizes a stateless model with only one active server and multiple passive servers the implementation of such solution is not trivial. To solve the issue of business continuity and to insure application is available at all times please refer to Control-M High Availability (HA) solution in the documentation. With Control-M HA one can install a primary and a secondary environments to handle failover scenario when of the two environments fail. Enterprise Manager gateway will automatically manage the connection between the two Control-M/Servers. Q. Can one use a NLB between Control-M/Enterprise Manager and Control-M/Server to simplify the network routing between the two Control-M/Server components regardless of where the Control-M/Server is hosted, in AWS. From Control-M/Server point of view, we do not see any problem that the EM will connect to the Control-M/Server via a Network Load Balancer (NLB). As long as the requests from EM reach the Control-M/Server they will be answered. The Control-M/Server is not effected by the hostname that is used when EM connects. The EM can connect using IP address, full qualified name, short name or host alias defined on the EM host. Therefore there is no problem that the EM will connect to Control-M/Server via NLB. The NLB provides no additional benefit with regards to handling a failover scenario since the Gateway knows how to manage connection properties of two Control-M/Servers. Q. Requirements for using Elastic Load Balancing ELB with Control-M/Agent agents. In order to define an ELB as Control-M/Agent loadbalancing gateway one need to configure Network Load Balancer to support ICMP protocol. Implementation wise ELB needs to be part of a security group that has ICMP protocol enabled. See whitepaper attached section "Submitting jobs behind ELB" Q. Does Control-M EM 9.0.21 version supports Amazon Linux 2022? A: Yes - Please see the OS Note in SPAC for details Q. Does Control-M EM 9.0.21 version support Amazon EKS? A: The Amazon EKS is not tested and not supported for Control-M/EM and Control-M/Server. Q. Is the use of Public IP recommended for Control-M/Enterprise Manager and Control-M/Server A. As EC2 instances are constantly recreated with new hostnames, the use of Public IP can create persistence for communication between EM clients and EM Server, between EM server and Control-M/Server and between Control-M/Server and Agents. Additional Information: |