Skip to main content Skip to complementary content

Launching an EC2 instance for Talend Administration Center and Nexus

In this article, the Talend Administration Center and Nexus repository have been installed on the same EC2 instance.

Procedure

  1. Connect to EC2 console in any region and click on Launch Instance.
  2. Choose AMI: Microsoft Windows Server 2012 Base for this demo. Any Talend supported OS type can be used in this demo.

    For further information, see the online publication about compatible Operating Systems.

  3. Select m4.large (or m4.xlarge if a more performing machine is needed) and configure Instance details:
    1. Network: Choose your VPC (use default if you don’t have specific VPC configured)
    2. Subnet : No preference
    3. Auto-assign Public IP : Disable (you will configure Elastic IPs later to use static IP address)
    4. Other options as default
  4. Add Storage : use Size 50 GiB and General Purpose SSD Volume Type (give you enough disk space for OS and Talend installation).
  5. Add Tag : Key:NameValue:TalendRuntimeAutoScaling-TAC&Nexus
  6. Configure Security Group: Create a new Security Group as below (only for this demo, you should have more strict rules in real case).
    1. Inbound:
    2. Outbound:
  7. Launch the EC2 instance once all configured. Once the instance created in EC2 dashboard, select the Elastic IPs option on AWS EC2 interface to configure static IP address for Talend Administration Center EC2 instance.
  8. Select Allocate new address and then choose the new created Talend Administration Center EC2 Instance Id. Once configured, you will find similar allocation information as shown below:

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 – let us know how we can improve!