Runtime Environments > Elastic runtime environments > Working with elastic runtime environments

Working with elastic runtime environments

You can create, modify, or remove elastic runtime environments as necessary. You can remove an environment only if it isn't used in a connection, task, or process.

You can perform the following actions on an elastic runtime environment:

Creating an elastic runtime environment

You can create as many elastic runtime environments as necessary, each with a different configuration.

1In Administrator, select Runtime Environments.

2Click New Runtime Environment.

3Enter the name of your elastic runtime environment.

4Select Elastic Runtime Environment as the environment type.

5Optionally enter a description for your environment.

6Click Next.

7Select the services and connectors to enable for this runtime environment. By default, no components are enabled.

For more information about the services, see Secure Agent Services. For more information about the connectors, see Connections.

8Click Create.

Next, configure your environment and services.

- To configure your environment, see Environment configuration. You must configure your environment before you can use it.
- To configure your services, see Service configuration. This step is optional and is necessary only if you need to change some service properties values or set a custom service configuration.

If you need to make changes to your environment name or description, see Editing environment properties. Your environment details are displayed on the Overview tab.

Environment configuration

Configure specific details about your elastic runtime environment on the Environment Configuration tab.

The environment configuration deals with the infrastructure where the elastic runtime environment containers will be deployed. It also defines how these containers can take inputs (for example, associated EBS storage types and values) and write outputs to locations such as logs.

Configure the Platform Configuration and Advanced Configuration tabs as necessary. You must configure at least your platform.

Platform Configuration tab

The following table describes the Platform Configuration fields.

Field	Description
Region	Region in which to create the cluster. Use the drop-down menu to view the regions that you can use.
Worker Instance Type	Instance type to host the worker nodes. Use the drop-down menu to view the instance types that you can use in your region. For information to verify that the instance type that you select from the drop-down menu is supported in the selected availability zones and your AWS account, refer to the AWS documentation.
Worker Instance Profile	Instance profile to be attached to the worker nodes. The name must consist of alphanumeric characters with no spaces. You can also include any of the following characters: _+=,.@-
Number of Worker Nodes	Number of worker nodes in the cluster. Specify the minimum and maximum number of worker nodes.
Worker Node Idle Timeout	Specify the amount of idle time before before a worker node times out.
Enable High Availability	Select this option to indicate that the cluster is highly available. An odd number of master nodes will be created based on the number of availability zones or subnets that you provide. You must provide at least three availability zones or subnets. For example, if you provide six availability zones, five master nodes are created with each master node in a different availability zone. Note: When you provide multiple availability zones or subnets, worker nodes are highly available. Worker nodes are created across the availability zones or subnets regardless of whether high availability is enabled. For more information about high availability, refer to the Kubernetes documentation.
EBS Volume Size	Size of the EBS volume to attach to a worker node for temporary storage during data processing. The volume size scales between the minimum and maximum based on job requirements. The range must be between 50 GB and 16 TB. By default, the minimum and maximum volume sizes are 100 GB. This configuration property does not apply to Graviton-enabled clusters, as Graviton does not support storage scaling. Note: When the volume size scales down, the jobs that are currently running on the cluster might take longer to complete.

The following table describes the System Storage fields. Configuring system storage can improve mapping performance in Data Integration.

Field	Description
Type	Only EFS disks are supported.
File System	The file system is the file system ID of the EFS disk.
Source Mount	File system path to be mounted in the elastic runtime environment.
Access Point	The ID of the Amazon EFS file system access point. The access point ensures isolation for tenants in a multi-tenant EFS file system. Once an access point is set up, you can configure the file system policy to allow access only to the access point for the IAM role.

The following table describes the Data Storage fields. Configuring data storage allows you to access files in EFS directories.

Field	Description
Type	Only EFS disks are supported.
File System	The file system is the file system ID of the EFS disk.
Source Mount	File system path to be mounted in the elastic runtime environment.
Access Point	The ID of the Amazon EFS file system access point. The access point ensures isolation for tenants in a multi-tenant EFS file system. Once an access point is set up, you can configure the file system policy to allow access only to the access point for the IAM role.

Advanced Configuration tab

Advanced technical users can further customize their elastic runtime environments in the Advanced Configuration tab. The following table describes the advanced configuration properties.

Configuration	Description
Initialization Script Path	Enter the Amazon S3 file path of the initialization script to run on each cluster node when the node is created. Use the format: <bucket name>/<folder name> The script can reference other init scripts in the same folder or in a subfolder. The script must be a bash script.
Cloud Ecosystem Tags	Define tags to describe the cloud ecosystem. At least one tag is required, but the value can be empty.
Runtime Properties	Configure properties to customize the cluster and the jobs that run on the cluster. At least one tag is required, but the value can be empty.

Service configuration

Use the Service Configuration tab to modify the default values of the service properties or apply a custom configuration to an elastic runtime environment.

Note: Don't change any of the service properties unless you are an advanced technical user or you have been directed by Informatica Global Customer Support. Incorrect settings can affect the operation of your system. You can use the reset icon to reset all values to their initial system defaults.

Service Configuration

The list displays all the properties for the services in use in your elastic runtime environment.

Click the edit icon to change the value of any property or flag a property as sensitive. Click the save icon to save the changes.

Note: Your entries aren't validated, so check your values carefully before saving.

If no services are enabled yet, click Enable Services and Connectors to enable them now. For more information, see Service and connector assignment for elastic runtime environments.

Custom Configuration

If you need to add a new service property, use the Custom Configuration tab.

Click the add new row icon and then complete the fields. Click the save icon to save the changes.

Monitoring an elastic runtime environment

Use the Monitor tab to check the state of your elastic runtime environment and take any corrective actions as necessary. For example, you may find that you need to change the number of worker nodes to scale up or scale down the environment as needed.

1In Administrator, select Runtime Environments.

2Select your elastic runtime environment from the list.

3Select the Monitor tab.

Review the audit log and take any necessary actions. Use the filter control to quickly locate specific audit entries by date, instance, or component. Click the refresh icon to update the list.

The image shows the Monitor tab for an elastic runtime environment. The audit log includes columns for Date, Instance Name, Component Name, Type, and Message. There are also icons for filtering and searching the log, and for refreshing the audit log display.

Editing environment properties

You can rename an elastic runtime environment or change its description at any time.

1In Administrator, select Runtime Environments.

2Select the Edit Environment Properties action for your elastic runtime environment.

3Modify the environment's name or description as required.

You can't change the environment type. If you want to change the environment to a Secure Agent group, delete the elastic runtime environment and create a new Secure Agent group.

4Click OK.

Deleting an elastic runtime environment

You can delete an elastic runtime environment that's no longer required. Ensure that this environment is not used anywhere before deleting.

1In Administrator, select Runtime Environments.

2Select the Delete action for your elastic runtime environment.

3Click OK to confirm.

A message either confirms the deletion was successful or deletion is not possible. If the deletion failed, use the Viewing elastic runtime environment dependencies action to locate the assets still using this environment and then change it to another environment.

Viewing elastic runtime environment dependencies

You can view object dependencies for an elastic runtime environment.

The Dependencies page displays the connections and tasks that use the elastic runtime environment, as well as the objects that the environment uses. If you need to delete an elastic runtime environment, this page helps you identify where the environment is being used, so that you can disconnect the environment first.

1In Administrator, select Runtime Environments.

2Select the Show Dependencies action for your elastic runtime environment.

The Uses tab displays the objects that the elastic runtime environment uses. The Used By tab shows the objects that use the environment.

This image shows the Dependencies tab of an elastic runtime environment. It displays examples of a connection and mapping task that is using the environment. The dependency details include columns for: Name, Type, Location, Updated By, and Status.

To sort the objects that appear on the page, click the Sort icon and select the column name for the property you want to sort by.

To filter the objects that appear on the dependencies page, click the Filter icon. Use filters to find specific objects. To apply a filter, click Add Field, select the property to filter by, and then enter the property value. You can specify multiple filters. For example, to find connections with Oracle in the name, add the Type filter and specify Connection. Then add the Name filter and enter "Oracle".

Setting permissions for an elastic runtime environment

You can limit access to an elastic runtime environment based on users or groups.

The Permissions page lists the users and groups who can interact with the elastic runtime environment and how they can interact (Read, Update, Delete, Execute, Change Permissions). If no users or groups are specified, that means there are no permissions restrictions on the elastic runtime environment.

1In Administrator, select Runtime Environments.

2Select the Permissions action for your elastic runtime environment.

The permissions are organized within the Users and Groups tabs.

3To add a user or group:

aMake sure you're in the right tab, then click Add.
bSelect the user or group to add. Use the Find box to help you if the list is long. You can only add one user or group at a time.
cClick Add.
dSet the permissions for the user or group. The following table describes the permissions you can set:

Permission	Description
Read	View details about the elastic runtime environment and use the elastic runtime environment in a task.
Update	Edit the elastic runtime environment.
Delete	Delete the elastic runtime environment.
Execute	Run the elastic runtime environment.
Change Permissions	Change permissions for the elastic runtime environment.

eClick Save.

This image shows the Permissions tab of an elastic runtime environment. The permissions are divided across Users and Groups subtabs. For each user or group, it displays the permissions, with check boxes for Read, Update, Delete, Execute, Change Permissions. There is one sample user on the page.

4To remove a user or group:

aSelect the users or groups to remove.
bClick Remove.