Creating Remote Engine Gen2

Procedure

Open the Engines tab of the Processing page.
Click Add and select Remote Engine Gen2 .
Select the environment in which to create the engine.
Select the workspace to which you want to assign your engine.
By default, engines can be used in all the workspaces of the environment.

To restrict the access to the engine, allocate the engine to be available in only one specific workspace. Only users with the Execute permission on the workspace can access and use the engine.
Enter the name of the engine, for example my-remote-engine.
Optional: Enter the description of the engine.
Click Save.
The Remote Engine Gen2 is added to the list in the Engines tab of the Processing page. The engine is in Not paired state.
Click the name of the engine to access the Engine details page.
Copy the Pair key to your clipboard. In the products and the documentation, this key is also referred to as a pre-authorization key or pre-authorized key.
The key is required when creating the Remote Engine Gen2 either in your Amazon Web Services (AWS) or Microsoft Azure account or when installing it locally.

Install the Remote Engine Gen2:

If you install it manually using the execution script:
1. Click Downloads for installation to go to the Downloads page.
2. Install and pair the engine locally or on your Virtual Private Cloud.
The storage disks attached to the Amazon EC2 instance of the Remote Engine Gen2 are not encrypted by default.
Availability-noteDeprecated
If you install it in your AWS account, create the engine using CloudFormation. When it is up and running, it will be automatically paired.
Availability-noteDeprecated
If you install it in your Azure account, create the engine using the pre-configured form provided by Talend. When it is up and running, it will be automatically paired.

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