Deploy the elastic runtime environment on AWS to make the Kubernetes cluster available to process data from Informatica Intelligent Cloud Services.
Complete the following tasks:
1SSH into the master node so that you can download and run the cluster installer.
2Clean up resources if you're redeploying an elastic runtime environment.
3Download the cluster installer to get the config.txt file for the installation and the installation script.
4Create a directory on the master node for the elastic runtime environment.
5Update the config.txt file to provide details about your AWS environment and Informatica Intelligent Cloud Services account to the cluster installer.
6Run the cluster installer to deploy the elastic runtime environment.
7Mount each EFS file system on the master node.
8Verify that the elastic runtime environment is running by checking the status of the Data Integration Server and cluster nodes in Administrator.
Step 1. SSH into the master node
SSH into the master node so that you can download and run the cluster installer.
1Optionally, SSH into the jump host.
aContact your organization's IT team to create a passphrase for the private key on your local machine and configure the jump host to authenticate using the public key.
bSSH into the jump host from your local machine by running the following command:
ssh -i <private key name>.pem <user name>@<jump host public IP address>
2SSH into the master node by running the following command:
ssh -i <private key name>.pem cloud-user@<master node private IP address>
Step 2. Clean up resources
If you're redeploying an elastic runtime environment, run the cluster uninstaller to clean up AWS and Kubernetes resources.
Note: Run the cluster uninstaller only after you have run the cluster installer. If you haven't run the cluster installer, the uninstaller fails.
1Before you run the uninstaller, verify that there are no jobs running on the elastic runtime environment. Running the uninstaller is irreversible and terminates any running jobs.
2To run the uninstaller, run the following command on the master node:
./cluster_uninstall.sh
The cluster uninstaller deletes resources including Auto Scaling groups, EC2 instances, launch templates, and secrets.
Step 3. Download the cluster installer
Download the cluster installer to get the config.txt file for the installation and the installation script. You can download the cluster installer from Administrator or on the master node.
Download the cluster installer from Administrator
To download the cluster installer from Administrator, perform the following steps:
1In Administrator, open the Runtime Environments page.
2Select Download Runtime Installer.
3Select Elastic as the Environment Type.
4Select Download. The ZIP file that contains the cluster installer is downloaded to your local machine.
Download the cluster installer on the master node
To download the cluster installer on the master node, perform the following steps:
1On the master node, create a directory for the elastic runtime environment by running the following command:
mkdir ert
2Navigate to the directory by running the following command:
cd ert
3Download the cluster installer by running the following command:
Step 4. Create the cluster installer directory on the master node
Create a directory on the master node for the elastic runtime environment.
1On the master node, create a directory for the elastic runtime environment by running the following command:
mkdir ert
2Copy the cluster installer into the ert directory.
3Navigate to the directory by running the following command:
cd ert
4Unzip the file by running the following command:
unzip cluster-installer.<version>.zip
Step 5. Update the config.txt file
Update the config.txt file to provide details about your AWS environment and Informatica Intelligent Cloud Services account to the cluster installer.
In the elastic runtime environment directory on the master node, open the config.txt file by running the following command:
vi config.txt
The following table describes the values to update in the config.txt file:
Variable
Description
IDS_HOST
Domain for the POD for your organization. For example: dm-us.informaticacloud.com. To locate the domain, find your POD in POD Availability and Networking and copy the property from the Login URL field.
USER
Informatica Intelligent Cloud Services user name.
PASS
Informatica Intelligent Cloud Services password.
runtimeEnvironmentId
Elastic runtime environment ID.
To find the ID, navigate to the Runtime Environments page in Administrator, copy the elastic runtime environment ID from the URL.
For example, in the URL https://usw1.dmr-us.informaticacloud.com/cloudUI/products/administer/main/elastic-agent/KUBERNETES/0141GU25000000000002/overview, the elastic runtime environment ID is 0141GU25000000000002.
PROXY_USER
Optional. User name to connect to the outgoing proxy server.
PROXY_HOST
Optional. Host name of the outgoing proxy server that the Secure Agent uses.
PROXY_PORT
Optional. Port number of the outgoing proxy server.
majorVersion
Release version. For example, use 202507 for the July 2025 release.
SECURITY_GROUP_NAME
Name of the the security group that allows access to the elastic runtime environment.
If any required inbound rules are missing and the cluster installer role has permissions to modify security groups, the cluster installer populates them and continue the installation. Otherwise, cluster installation stops. To continue the installation, edit the security group manually and add the required inbound rules.
Note: If your organization uses an outgoing proxy server to connect to the internet, the elastic runtime environment connects to Informatica Intelligent Cloud Services through the proxy server. You can configure the proxy server settings in the config.txt file. When the cluster installer runs, it prompts you for the proxy server password. The proxy server settings can't be changed after the elastic runtime environment is deployed.
The config.txt file includes the following information:
# Distributed Configuration for Cluster Installer # ================================================= # Customize the following variables to match your environment. # # IDS_HOST # The host address or URL for the IDS service. export IDS_HOST="<POD URL like dm-us.informaticacloud.com>" # USER # Informatica Intelligent Cloud Services user name for the organization that you want to log in to. export USER="<IICS user name>" # PASS # Informatica Intelligent Cloud Services password. export PASS="<IICS password>" # runtimeEnvironmentId # A unique identifier for your runtime environment. export runtimeEnvironmentId="<elastic runtime environment ID from Administrator>" # PROXY_USER PROXY_HOST PROXY_PORT # Specify these values if your organization uses HTTP proxy for outbound communication. # You will be prompted to enter Proxy password by the cluster installation script if PROXY_USER is specified. export PROXY_USER=<proxy server user name> export PROXY_HOST=<proxy server host name> export PROXY_PORT=<proxy server port number> # # majorVersion # Major version number for your release. Update as needed. export majorVersion=<version like 202507>
# Following variables are provided so that you can customize cluster creation as per your organization policies. # # KEY_PAIR_NAME and KUBE_CONFIG_SECRET_NAME # These values identify the key pair and its secret name used to access your cluster. # Name of the Key Pair that is used to login to the nodes in the cluster KEY_PAIR_NAME="idmc-elastic-rte-key-pair" KUBE_CONFIG_SECRET_NAME="idmc-elastic-rte-kube-config" # # ORG_ADMIN_CREDS_SECRET_NAME # The name of the secret that stores organization administrator credentials. ORG_ADMIN_CREDS_SECRET_NAME="idmc-elastic-rte-org-creds" # # SECURITY_GROUP_NAME # The security group name defined for access within your environment. SECURITY_GROUP_NAME="<security group name like sg_ert>" # # NODE_NAME_PREFIX # Prefix for naming the nodes in your cluster. NODE_NAME_PREFIX="idmc-elastic-rte" # # AGENT_APP_LAUNCH_TEMPLATE_NAME and AGENT_APP_ASG_NAME # Launch template and auto scaling group names for the agent application. AGENT_APP_LAUNCH_TEMPLATE_NAME="idmc-elastic-rte-agent-app-launch-tmpl" AGENT_APP_ASG_NAME="idmc-elastic-rte-agent-app-asg" # # JOB_NODE_LAUNCH_TEMPLATE_NAME and JOB_NODE_ASG_NAME # Launch template and auto scaling group names for job nodes. JOB_NODE_LAUNCH_TEMPLATE_NAME="idmc-elastic-rte-job-node-launch-tmpl" JOB_NODE_ASG_NAME="idmc-elastic-rte-jon-node-asg" # # CONTROL_PLANE_ELB_NAME # The load balancer name for the control plane in high-availability setups. # Used only when High Availability (HA) mode is enabled. CONTROL_PLANE_ELB_NAME="idmc-elastic-rte-control-plane-elb" # # efsNameTag # Tag for EFS (Elastic File System) shared storage to added upon creation export efsNameTag="idmc-elastic-rte-efs-name" # # IS_RUNNING_ON_MASTER # Set to false if this script is not executed on the master node; otherwise, leave as true. IS_RUNNING_ON_MASTER=true # # VPC_NAME # Provide the VPC name if the script is not running directly on the master node. VPC_NAME="<VPC name like vpc_ert>" # # resourceCreationLogFile # Log file name where created resources will be recorded. export resourceCreationLogFile="resource_creation_log.txt"
Step 6. Run the cluster installer
Run the cluster installer with or without a proxy to deploy the elastic runtime environment.
Run the cluster installer with a proxy
To run the cluster installer with a proxy, complete the following tasks:
1Run the following command:
./create_cluster_nodes_ha.sh
2Enter your password on the Enter proxy password line. When you type in your password, the characters are hidden for security purposes.
Note: Using Ctrl + C while running the installer in proxy mode terminates the installation.
Run the cluster installer without a proxy
To run the cluster installer without a proxy, complete the following tasks:
1Run the following command on the master node:
nohup ./create_cluster_nodes_ha.sh &
2To monitor the installation process, run the following command:
tail -f nohup.out
Step 7. Mount the EFS file systems on the master node
Mount each EFS file system on the master node. For information about mounting an EFS file system, refer to the AWS documentation.
Step 8. Verify that the elastic runtime environment is running
Verify that the elastic runtime environment is running by checking the status of the Data Integration Server and cluster nodes in Administrator.
1In Administrator, open the Runtime Environments page.
2Expand the elastic runtime environment.
3Verify that the Data Integration Server is running and that one or more instances are running.
Note: It might take a few minutes for the Data Integration Server to start the instances.