Learn how to deploy Control-M 9.0.00 in the cloud using Amazon Web Services.  During this webinar, we will cover: Installation media for Cloud, Supportability, and Settings & Installation procedure.  Come learn how you can address your changing business needs by utilizing the public cloud enterprise job scheduling capability with Control-M.


In this webinar Ted Leavitt will explain and demonstrate how to deploy Control-M on AWS.


This is the link on YouTube for the recorded session:


Connect with Control-M: Deploying Control-M 9.0.00 on AWS - YouTube


Here is the Q&A for this webinar (Connect With Control-M: Deploying Control-M 9.0.00 on AWS)




Q: What is the official support policy for AWS cloud?
A: Control-M deployment on AWS and Azure is supported with current release.
We support running Control-M with internal
PostgreSQL Database
Oracle Database
PostgreSQL RDS
Oracle RDS


Q: What is minimum Control-M version and FP level required on Cloud platform?
A: Control-M/Enterprise Manager V9.0.00 FP400
Control-M/Server V9.0.00 FP300


Q: Which installation media should be used for Cloud platform?
A: BMC offers two versions of Control-M installation media. One is for regular installation use, another named with 'Control-M Version 9.0.00 with cloud support V2' for Cloud platform.


Q: How do I connect an Agent on AWS to Control-M/Server on premise host across the internet?
A: We assume the premise Server can initiate a TCP/IP connection to the agent machine (at AWS), and Agent on AWS cannot initiate a TCP/IP connection to server. The ideal solution for this scenario is using persistent connection where the Control-M/Server is connecting to the agent. The agent should be configured for "Allow communication". The only port that should be opened is the "Server to Agent" port on the agent machine as inbound.


Q: Is there a dedicated AMI in AWS that we can use that has Control-M binaries baked into it? In AWS Marketplace?
A: We do have an AMI, but we do suggest launching an EC2 image and installing Control-M in that image because of limitations of the current Control-M AMI.


Q: Can EIP be allocated for RDS Database?
A: You cannot assign an elastic IP to an RDS instance. Please note that RDS provides you with a DNS endpoint using which you can connect to your database instance. This DNS endpoint will not change during the lifetime of your instance. This ensures that then you do not have to reconfigure your application's database connection endpoints as long as you're using the same database instance.


Q: For RDS DB, should we enable the AWS automated backup?
A: It’s your own preference, and the Control-M embedded Backup/Restore solution are still recommended while AWS automated backup is a good supplement.


Q: For RDS DB, should we enable RDS DB Auto minor version upgrade?  Will it affect Control-M?
A: It will not affect Control-M, as long as the major RDS DB version is compatible with Control-M.


Q: Is Amazon Linux compatible with Control-M?
A: EM server and CTM/Server are not supported.  Control-M/Agent 9 Fix Pack 2 supports Amazon Linux 2015.09.x (64 bit) and later with the following prerequisites:
* ksh-20120801-19.el7.x86_64.rpm
* compat-libstdc++-33-3.2.3-61.x86_64.rpm


Q: Can we upgrade from old Control-M normal installation to V9 in AWS?
A: Yes you can.


Q: Does Control-M support Multi Subnet which is needed and widely used in AWS?
A: At moment, we don't support it. We have already a RFE to address this.


Q: Does control-M support AWS s3 file transfer protocol?
A: At this time AFT does not support working with AWS S3. It is planned to be included in future functionality of our Managed File Transfer product. It has not been announced when this will be included in a future release.


Q: Does control-M support Elastic File System (EFS)?
A: Yes, Control-M server V9 and Agent v9 support EFS


Q: If I have an on premise Control M, can we use the existing software distro after installing the Fix Packs, or do we need the cloud media? Do we need a new license for this?
A:  The existing media (DROST) can be used to install the Control-M in a non-cloud environment.  We do recommend using the "with cloud support V2" media for installing in cloud.  Fix Packs can be applied to both of these installations.  We would advise speaking with your account rep regarding any licensing or entitlement.


Q: How is the HA and DR handled for Control-m 9.0 on two distinct regions?
A: As long as the two hosts have connectivity between one another, it behaves no different than HA or DR on-prem.  With HA, there are complications if there is significant latency between the different hosts (and their databases).


Q: Is it must to have elastic IP while creating an instance or while choosing from the AWS marketplace?
A: It’s not a "must", but it is highly recommended.  If you do not have an EIP or configured VPC, the public IP of the Control-M host will change with each restart, requiring the EM (CORBA) configuration to be updated to reflect the new public IP.


Q: What considerations are there for a mixed AWS environment, where for instance, the EM is installed on the corporate network with some Control-M Servers in AWS and some on company network?
A: The main consideration in such a scenario is the networking.  You must ensure proper connectivity between any hosts on the corporate network and those running in the cloud.


Q: what is the minimum space required for the server to install correctly on AWS or was this discussed earlier?
A: The installation guide states a requirement of 100 GB for installation of Control-M on a UNIX host.  This should be sufficient for the base installation and the subsequent installation of the required Fix Packs and patches.


Q: Can an on-premises Control-M EM server manage both on-premises Control-M servers and AWS Control-M Servers at the same time?
A: Yes, it is not a problem.


Q: What’s the Control M AWS media file format? Is it downloadable?
A: The installation media is available in ISO format as well as zip for Windows and tar.Z for UNIX.


Q: Can we have v8 in on premise while installing v9 in AWS?
A: Yes, normal considerations of working with different versions of Control-M would be to be taken into account.


Q: How are the Control-M Agents connected to East Region's Control-M/Server will connect in case of DR to the Control-M/Server in the west region?
A: This will work the same as an on-prem installation.  If the Control-M/Server fails-over, when it initiates communication with the M/Agent, it will use its name and the M/Agent will update its primary M/Server to that new name.  There must be network connectivity between the M/Server and M/Agent.


Q: Can we ftp the iso image from local desktop environment to EC2?
A: Yes as long as the ftp is enabled at your AMI and allowed by your corporate network.  Typically it would be easier to scp or sftp the image, as this is enabled by default in the Linux EC2.



Q: Can primary and secondary CONTROL-M AWS instances be installed in Amazon data centers in different time zones?  Are there any specific configuration issues for this configuration?
A: The same considerations would need to be made as performing an installation on-prem.  It would generally be advisable to have an HA/DR pair configured for the same time zone to avoid confusion.