Launching the execution script

Procedure

Go to the Remote Engine Gen2 installation directory.
Run the following command to launch the executable file:
./remote-engine.sh start -r <region> -k <pair_key>
- <region> corresponds to the region of your Talend Cloud account.
- <pair_key> corresponds to the Pair key you have previously copied from Talend Management Console
Information noteTip: To display the list of available regions of your Remote Engine Gen2, run the -h or --help :
- us, eu, ap, and au corresponds to the AWS US, AWS Europe, AWS Asia-Pacific, and AWS Australia regions respectively
- us-west corresponds to the Azure region
If you want to use the data API feature of Talend Cloud Data Inventory, you need to start the Remote Engine Gen2 with a compatible profile, using the following command: sudo ./remote-engine.sh start -r <region> -k <pair key> -p data-apis.

Results

The Remote Engine Gen2 instance is created and running in the specified account region.

The <pair_key> parameter is not mandatory and is only required the first time you start the engine in order to pair it. Type in remote-engine.[bat|sh] stop or remote-engine.[bat|sh] restart to stop or restart the Remote Engine Gen2.

Note: You can only use the restart command if the application is still running. If it is down, you need to use the start command.

What to do next

Connect to Talend Management Console, go to the Engines tab of the Processing page and check that the Remote Engine Gen2 status went from Not paired to Paired.

Note: Once your engine is paired, it may take several minutes to be ready to be used in Talend Cloud Pipeline Designer. During this time, the engine will appear as unavailable.

Screenshot showing Remote Engine Gen2 as paired.

Now that your Remote Engine Gen2 is ready, you can:

create a run profile from Talend Management Console.
use your Remote Engine Gen2 to create connections, datasets or execute pipelines and preparations in the Talend Cloud apps.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here