Connections > REST V2 connection properties > Configure the elastic runtime environment
  

Configure the elastic runtime environment

When you use the elastic runtime environment, you can configure TLS authentication and establish one-way or two-way secure communication with the REST API.
Ensure that the certificates are in the .jks format.
To configure a secure REST V2 connection using the elastic runtime environment, complete the following prerequisite tasks:
  1. 1Deploy the elastic runtime environment on AWS to make the Kubernetes cluster available to process data from Informatica Intelligent Cloud Services.
    2. For more information about deploying an elastic runtime environment, see Deploy an elastic runtime environment.
  2. 2Ensure that the elastic agent is up and running and enable the required connectors.
    3. To enable connectors in the elastic agent, perform the following steps:
    1. aIn Administrator, select Runtime Environments.
    2. bRight-click the Secure Agent group and select Enable or Disable Services and Connectors.
      3. A dialog box listing all the services and connectors for the Secure Agent group is displayed.
    3. cOn the Connectors tab, enable the required connectors.
    4. dClick OK.
  3. 3Create a data disk in the same environment where the elastic runtime cluster is running to store the custom binaries.
  4. 4On the master node, create a directory and mount the EFS or data disk to that directory.
  5. 5Place the custom binaries on the mounted disk and copy the exact path to the binaries.
    6. This path is used in POST API calls.
  6. 6Log in to Informatica Intelligent Cloud Services and obtain the session ID and runtime environment ID.
  7. 7Make a POST call to the REST API, passing the session ID, runtime environment ID, and the binary file path to register the binaries.
    8. For more about information about making the POST calls, see Supplementary files in the REST API Reference guide.
    The following is an example of the POST request:
    POST <base URL>/api/v3/RuntimeEnvironment/<runtime environment ID>/ElasticConfig
    Content-Type: application/json
    Accept: application/json
    INFA-SESSION-ID: <SessionId>
    {
    "rteId": "rte-12345",
    "specification": {
    "agent": {
    "dataIntegrationServer": {
    "restv2": {
    "swaggers": [{"sourcePath": "/<path to binaries>/swagger.json"}],
    "keystores": [{"sourcePath": "/<path to binaries>/keystore.jks"}],
    "truststores": [{"sourcePath": "/<path to binaries>/truststore.jks"}]
    }
    The POST call triggers a restart of the Data Integration Server.
  8. 8Verify that the elastic runtime environment is running by checking the status of the Data Integration Server in Administrator.
  9. 9Test a connection or run a mapping to confirm that the elastic runtime environment can access and use the custom binaries.