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

Working with elastic runtime environments

After you create an elastic runtime environment, you can edit, monitor, and delete it. You can also view dependencies and change permissions.
You can perform the following tasks:
Change the name or description of the environment.
To change the name or description of your elastic runtime environment, expand the Actions menu and select Edit Environment Properties.
Update the environment configuration.
To update the environment properties, drill down on the elastic runtime environment and edit the properties on the Environment Configuration tab.
After you update the property values and save the configuration, it takes some time for the changes to take effect in the deployed elastic runtime environment. To verify certain changes, you can view the lifecycle graph in Administrator or view the logs on your AWS account.
Enable or disable services and connectors.
You can enable a service to allow the elastic runtime environment to run product features associated with the service. You can enable specific connectors to allow the environment to communicate with cloud and on-premise applications, platforms, databases, and flat files.
To enable services and connectors, expand the Actions menu and select Enable or Disable Services, Connectors.
Configure Secure Agent services.
You can configure Secure Agent services or change service properties to optimize performance or if you are instructed to do so by Informatica Global Customer Support.
Modify Secure Agent service properties on the Service Configuration tab or add custom properties for Secure Agent services. Select Reset to reset the Secure Agent service properties to their system defaults.
For more information about the Secure Agent services and their properties, see Secure Agent Services.
Delete the environment.
You can delete an elastic runtime environment if it has no running instances.
To clean up instances, run the cluster uninstaller. For more information, see Step 2. Clean up resources.
To delete an elastic runtime environment, expand the Actions menu and select Delete.
Monitor the audit log, nodes, and jobs.
To monitor an elastic runtime environment, drill down on the elastic runtime environment and open the Monitor tab. You can view the following details:
View images.
An elastic runtime environment uses images to start up Informatica Intelligent Cloud Services and Secure Agent services.
Informatica allows you to access its image repository so that you can download the images and scan them to ensure that they meet your enterprise-level security and compliance needs. Informatica notifies you when a new image is available so that you can scan the image before the deployment window for the next release.
To view the images that an elastic runtime environment uses, use one of the following options:
View dependencies.
View dependencies to find the tasks or connections that are using the elastic runtime environment or to find the objects that are used by the elastic runtime environment. To view dependencies, expand the Actions menu and select Show Dependencies.
Change permissions.
To change permissions for an elastic runtime environment, expand the Actions menu and select Permissions. You can define permissions for an elastic runtime environment for each user group in your organization.
The following table describes the permissions that 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.

Connectors in an elastic runtime environment

You can use connectors in tasks that run in an elastic runtime environment.
An elastic runtime environment can run tasks that use the following connectors:
  • - Amazon Athena
  • - Amazon Redshift V2
  • - Amazon S3 V2
  • - Ariba V2
  • - BigMachines
  • - Box
  • - Concur V2
  • - Coupa V2
  • - Databricks
  • - Eloqua REST
  • - File Processor
  • - Google Analytics
  • - Google BigQuery V2
  • - Google Cloud Storage V2
  • - IBM MQ
  • - JDBC V2
  • - JIRA
  • - JIRA Cloud
  • - Kafka
  • - Large Language Model
  • - LDAP
  • - Marketo V3
  • - Microsoft Azure Blob Storage V3
  • - Microsoft Azure Data Lake Storage Gen2
  • - Microsoft Azure Cosmos DB SQL API
  • - Microsoft Azure Synapse SQL
  • - Microsoft Dynamics 365 for Operations
  • - Microsoft Dynamics 365 for Sales
  • - Microsoft Excel
  • - Microsoft Fabric Data Warehouse
  • - Microsoft Fabric Lakehouse
  • - Microsoft Fabric OneLake
  • - Microsoft SharePoint
  • - Microsoft SharePoint Online
  • - Microsoft SQL Server*
  • - MongoDB V2
  • - MySQL
  • - NetSuite
  • - NetSuite RESTlet V2
  • - OData Consumer
  • - OData V2 Protocol Reader
  • - OData V2 Protocol Writer
  • - ODBC
  • - Oracle*
  • - Oracle Autonomous Database
  • - Oracle Business Intelligence Publisher V1
  • - Oracle Cloud Object Storage
  • - Oracle CRM Cloud V1
  • - Oracle Financials Cloud V1
  • - Oracle HCM Cloud V1
  • - PostgreSQL*
  • - Quickbooks V2
  • - REST V2
  • - Salesforce
  • - Salesforce Data Cloud
  • - Salesforce Marketing Cloud
  • - Salesforce Pardot
  • - SAP ADSO Writer
  • - SAP BAPI
  • - SAP BW BEx Query
  • - SAP HANA
  • - SAP OData V2
  • - SAP OData V4
  • - SAP ODP Extractor
  • - ServiceNow
  • - Snowflake Data Cloud
  • - SuccessFactors ODATA
  • - SurveyMonkey
  • - Tableau V2
  • - Tableau V3
  • - Veeva Vault
  • - Web Service Consumer
  • - Workday V2
  • - Xero
  • - Zendesk V2
  • - Zuora AQuA
*Applicable only if deployed on Cloud instances.

Downloading images using the REST API

Download images from Informatica's image repository using the REST API so that you can scan them for vulnerabilities according to your compliance needs.
To download images, you need the "Elastic runtime environment - manage tokens" privilege in your organization. For more information about feature privileges, see User Administration. To run Docker commands, install Docker on the machine.
    1Use the platform REST API version 3 containerimagetoken resource to get a token for the image repository.
    You can create a token or use an existing token for your organization. For more information, see Getting a new token or Getting all tokens for an organization, respectively.
    2Use the platform REST API version 3 ais resource to get image information for the elastic runtime environment.
    For more information, see Getting runtime environment image information.
    3On the machine that you use to scan images, run the following Docker command to connect to the image repository:
    docker login infacloud-k8s-agent-docker-dev.jfrog.io --username <Informatica organization ID> --password <token value>
    4Run a Docker command to download the image.
    For example, the following command downloads version 64.1:
    docker pull infacloud-k8sagent-docker-dev-jfrog.io/Data Integration:64.1