Deploy Director AMIs

Overview

You can use the Director Amazon Machine Images (AMIs) to launch the following instances in the Amazon Web Services (AWS) platform:

1. Fabric Server

2. API Server

3. LPSM

This guide helps you access and deploy the Director AMIs in your AWS space.

Installation Sequence of Director AMIs

To install the Director AMIs:

1. Install the Fabric Server. To learn more, see the Installation of Fabric Server section.

2. Install the API Server. To learn more, see the Installation of API Server section.

3. Install LPSM. To learn more, see the Install Director LPSM section.

Version Compatibility for Director AMIs

To properly configure the Director AMIs, the versions of Fabric Server, API Server, LPSM and Logpoint must be compatible with each other, as listed below:

API Server	Fabric Server	LPSM	Director Console	Logpoint
v2.9.1	v2.9.1	v2.9.0	v2.9.1	v7.4.0 and later
v2.8.0	v2.8.0	v2.8.0	v2.8.0	v7.3.0 and later
v2.6.1	v2.6.1	v2.6.0	v2.6.0	v7.1.0 and later
v2.5.0	v2.5.0	v2.5.0	v2.5.0	v7.0.0 and later
v2.3.0	v2.3.0	v2.3.0	v2.3.0	v6.11.0 and later
v2.2.0	v2.2.0	v2.2.0	v2.2.0	v6.10.0 and later
v2.0.0	v2.0.0	v2.0.0	v2.0.0	v6.9.0 - 7.0.2

Director Installation

• To install Fabric Server, see Installation of Fabric Server.

• To install API Server, see Installation of API Server.

Director Upgrade

• To upgrade Director patches, see Upgrade Director.

Change Network Information

• To change network information, see Changing the Network Information.

Configure Public IP for Fabric Servers

• To configure public IP for Fabric Servers, see Configuring Public IP for Fabric Servers.

Access the AWS Account Number

While we provide AWS-specific instructions in this guide, it’s important to be aware that the AWS interface may change over time. To ensure you have the most up-to-date information and to navigate any potential changes in the AWS interface, we recommend referring to the official AWS documentation or AWS Support resources.

Access the AWS Account Number

1. Log in to AWS Management Console.

2. Click the Support in the top-right corner.

3. Click Support Center.

4. Your Account number is in the top-left corner.

Select the Deployment Region

Select the Deployment Region

1. Log in to AWS Management Console.

2. In the top-right corner, find your deployment region in the list and select it.

Receive the Director AMIs

Contact the Logpoint Sales team and provide your AWS Account Number and Deployment Region to receive the:

• Fabric Server AMI

• API Server AMI

• LPSM AMI

Deploy the Director AMIs

Deploy in the following order:

1. Fabric Server AMI

2. API Server AMI

3. LPSM AMI

• You must deploy the Fabric Server AMI and install the Fabric applications before deploying the API Server AMI.

• You must plan the IP addresses for the AMIs before configuring security groups.

• Zpool related SNMP and diagnostic metrics are unavailable for the Director AMIs.

• If you are deploying the Fabric Server AMI in cluster mode or scaling the Fabric Server instances, you must create a route table. A route table ensures the network traffic is directed correctly. To learn how, go to Creating a Route Table.

Configure Security Groups

1. Log in to AWS Management Console.

2. In All services, find and select EC2.

3. In Network & Security, find and select Security Groups.

4. Click Create security group.

5. Enter a Security group name and a Description. You cannot edit them once you create the security group.

6. Search and select the security group’s VPC (Virtual Private Cloud).

7. Add rule for Inbound rules and Outbound rules for the Director AMIs:

   a. Inbound Rules:

Type	Protocol	Port range	Source (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the Fabric Server from the specified sources.
Custom TCP	TCP	22	CIDR blocks or IP addresses	Connect to the Fabric Server using SSH from the API Server, LPSM, user’s machine, and Logpoint instances.
Custom UDP	UDP	1194	CIDR blocks or IP addresses of the API Server, LPSM, and Logpoint instances	Communicate with the Fabric Server.

Inbound Rules for a Fabric Server in Standalone Mode

Type	Protocol	Port range	Source (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the Fabric Server from the specified sources.
Custom TCP	TCP	22	CIDR blocks or IP addresses	Connect to the Fabric Server using SSH from the API Server, LPSM, user’s machine, and Logpoint instances.
Custom UDP	UDP	1194	CIDR blocks or IP addresses of API Server, LPSM, and Logpoint instances	Communicate with the Fabric Server.
Custom TCP	TCP	88, 464, 749, 750, 754, 2181, 2121, 8485, 9000, 10004, 10006, 50020, 50475, 51070, 2888, 3888	CIDR blocks or IP addresses	Communicate with the Fabric Server instance from other Fabric Server instances.
Custom UDP	UDP	88, 464, 750	CIDR blocks or IP addresses	Establish a connection to the Fabric Server instance from other Fabric Server instances.

Inbound Rules for Fabric Server Instances in Cluster Mode

Type	Protocol	Port range	Source (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the clients (API Server, LPSM, and Logpoint instances) from the specified sources.
Custom TCP	TCP	22	CIDR blocks or IP addresses	Connect to the clients (API Server, LPSM, and Logpoint instances) using SSH from the user machine and the Fabric Server.
Custom TCP	TCP	443	User machines’ IP addresses	Use clients’ (API Server, LPSM, and Logpoint instances) web services.

Inbound Rules for the API Server, LPSM, and Logpoint Instances in Standalone Mode and Cluster Mode

b. Outbound Rules:

Type	Protocol	Port range	Destination (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the specified sources from the Fabric Server.
Custom UDP	UDP	123	CIDR blocks or IP addresses	Connect to the NTP server.
Custom UDP	UDP	53	CIDR blocks or IP addresses	Connect to the DNS server.
Custom UDP	UDP	1193	Logpoint support’s IP address	Connect to Logpoint support.
All traffic	All	All	CIDR blocks or IP addresses of clients - API Server, LPSM, and Logpoint instances	Connect to API Server, LPSM, and Logpoint instances.

Outbound Rules for a Fabric Server Instance in Standalone Mode

Type	Protocol	Port range	Destination (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the specified sources from the Fabric Server instances.
Custom UDP	UDP	123	CIDR blocks or IP addresses	Connect to the NTP server.
Custom UDP	UDP	53	CIDR blocks or IP addresses	Connect to the DNS server.
Custom UDP	UDP	1193	Logpoint support’s IP address	Connect to Logpoint support.
All traffic	All	All	CIDR blocks or IP addresses of clients - API Server, LPSM, and Logpoint instances	Connect to API Server, LPSM, and Logpoint instances.
Custom TCP	TCP	88, 464, 749, 750, 754, 2181, 2121, 8485, 9000, 10004, 10006, 50020, 50475, 51070, 2888, 3888	CIDR blocks or IP addresses	Communicate with other Fabric Server instances.
Custom UDP	UDP	88, 464, 750	CIDR blocks or IP addresses	Establish a connection with other Fabric Server instances from this instance.

Outbound Rules for Fabric Server Instances in Cluster Mode

Type	Protocol	Port range	Destination (Custom)	Description
All ICMP - IPv4	ICMP	All	CIDR blocks, security groups, IP addresses, or prefix lists	Ping the clients from the specified sources.
Custom UDP	UDP	123	CIDR blocks or IP addresses	Connect to the NTP server.
Custom UDP	UDP	53	CIDR blocks or IP addresses	Connect to the DNS server.
Custom UDP	UDP	1193	CIDR block or IP address of the Fabric Server	Establish a connection to the Fabric Server.

Outbound Rules for the API Server, LPSM, and Logpoint Instances in Standalone Mode and Cluster Mode

Select an AMI and Launch the Instances

1. Log in to AWS Management Console.

2. In All services, find and select EC2.

3. In Images, select AMIs.

4. Select Private images in the drop-down next to the search bar.

5. Find the relevant AMI in the list and right-click it.

6. Click Copy AMI.

7. In Copy AMI:

   1. Select the Destination region.

   2. Enter a Name and a Description.

   3. Select Encrypt target EBS snapshots and select a Master Key to encrypt the target snapshots.

8. Click Copy AMI.

9. Select Owned by me from the drop-down next to the search bar.

10. Select the AMI and click Launch. You are redirected to the Launch instance wizard. To launch AMI without enabling EBS encryption, select Private Images from the drop-down, select the AMI, and click Launch.

11. Select a suitable Instance Type from the list.

    Type	vCPUs	Memory (GiB)
    t2.xlarge	4	16

    Type	vCPUs	Memory (GiB)
    t2.large	2	8

12. Click Next: Configure Instance Details.

13. Enter the Number of instances to launch.

14. Select the Network where you want to launch the AMI, also known as Amazon Virtual Private Cloud (VPC).

    1. You can also Create new VPC.

15. Select a Subnet for the AMI.

    1. You can also Create new subnet.

16. Select Auto-assign Public IP. AWS provides public IPv4 addresses to the instances in the default subnet.

17. Select a Shutdown behavior. Select:

    1. Stop to stop the instance at shut down.

    2. Terminate to delete the instance at shut down.

    3. Enable termination protection if you want to protect the instances from accidental termination.

       To learn what the other configurations options do, go to the AWS documentation.

18. Click Next: Add Storage.

19. Enter the Size (GiB) and select the Volume Type for your instance. You need at least 100 GiB for the Fabric Server and API Server instances and 80 GiB for the Logpoint and LPSM instances.

20. Click Next: Add Tags.

21. Click Add Tag to add a tag to your instances, volumes, and network interfaces. Tags improve your search or filter results.

22. Click Next: Configure Security Group.

23. In Assign a security group, select Select an existing security group.

24. Select the security group created earlier. For details, go to Configuring Security Groups.

25. Click Review and Launch.

26. Review the configurations and click Launch Instances.

27. Select Create a new key pair from the drop-down. You need a key pair to establish an SSH connection with the Director setup.

    1. If you already have an RSA key pair, select Choose an existing key pair.

28. Select RSA Key pair type.

29. Enter a key pair name and click Download Key Pair.

30. Click Launch Instances. You can click the instance ID to view the launch status.

If you have any issues, contact the Logpoint support team. They will need your Director support connection details to fix the issue.

Access Director AMIs

Access the Fabric Server Instance

1. Log in to AWS Management Console.

2. In All services, find and select EC2.

3. Click the Instances drop-down on the left and select Instances.

   If you deploy the Fabric Server instances in cluster mode, you must stop the source/destination check. To stop the source/destination check:

   1. Right-click the Fabric Server instance and select Networking >> Change source/destination check.

   2. Select Stop and click Save.

4. Select the Fabric Server instance and note the IPv4 address (Public IPv4 address or the Private IPv4 address) used in the security groups.

5. Open the command prompt in your local machine and browse to the folder where you have downloaded the key pair.

6. Execute the following command:

   chmod 400 <filename>

   Example:

   chmod 400 DirectorFabricV1.8.0.pem

7. Establish an SSH connection with the Fabric Server using the following command:

   ssh -i "<filename>" cmdr-admin@<Fabric_Server_IP>

   Example:

   ssh -i "DirectorFabricV1.8.0.pem" [email protected]

To learn how to install the Fabric Server instance in standalone or cluster modes, go to the Installation of Fabric Server section.

Create a Route Table

1. Log in to the Fabric Server Console.

2. Execute the ifconfig tun0 command.

3. Note the value of the inet addr parameter. You need this value to know the Fabric Server’s tunnel network address.

4. Calculate the tunnel network address using the value of inet addr - change the last octate of inet addr to 0 and set the subnet mask to 24.

   Example:

   inet addr: 10.57.3.1
   Tunnel network address: 10.57.3.0/24

5. Log in to AWS Management Console.

6. In All services, find and select EC2.

7. Click the Instances drop-down on the left and select Instances.

8. Click the Instance ID of your instance.

9. Click the VPC ID.

   Your route table and the Fabric Server instances must be in the same VPC.

10. Find the Main route table column and click the route table ID.

11. Click the Routes tab and click Edit routes.

12. Click Add route to add a new route.

13. Enter a Fabric Server instance’s tunnel network address as the Destination and its instance ID as the Target.

14. Click Save changes.

Access the API Server Instance

Deploy the Fabric Server instance and install the Fabric applications before accessing the API Server instance. To learn how, see the Installation of Fabric Server section.

1. Log in to AWS Management Console.

2. In All Services, find and select EC2.

3. In Instances, select Instances.

4. Select the API Server instance and note the IPv4 address (Public IPv4 address or the Private IPv4 address) used in the security groups.

5. Open the command prompt in your local machine and browse to the folder where you have downloaded the key pair.

6. Execute the following command:

   chmod 400 <filename>

   Example:

   chmod 400 APIServerV1.8.0.pem

7. Establish an SSH connection with the API Server using the following command:

   ssh -i "<filename>" cmdr-admin@<API_Server_IP>

   Example:

   ssh -i "APIServerV1.8.0.pem" [email protected]

For details, go to the Installation of API Server section.

Access Director Console

Install the API Server before accessing Director Console. For details, go to the Installation of API Server section.

1. Log in to AWS Management Console.

2. In All services, find and select EC2.

3. In Instances, select Instances.

4. Select the API Server instance and note the IPv4 address (Public IPv4 address or the Private IPv4 address) used in the security groups.

5. Enter the IPv4 address in your web browser and connect to Director Console.

   Example:

   https://<IPv4address>

6. Log in to Director Console using the following credentials:

   Username: root
   
   Password: <Instance ID>

   We recommend you change the password immediately after the first login.

7. Upload a Director license. For details, go to the Uploading a Director License section.

Access LPSM

1. Log in to AWS Management Console.

2. In All services, find and select EC2.

3. In Instances, select Instances.

4. Select the LPSM instance and note the IPv4 address (Public IPv4 address or the Private IPv4 address) used in the security groups.

5. Enter the IPv4 address in your web browser and connect to LPSM.

   Example:

   https://<IPv4address>

6. Log in to LPSM using the following credentials:

   Username: admin
   
   Password: <Instance ID>

   We recommend you change the password immediately after the first login.

7. Go to System >> System Settings >> General in LPSM and set the IPv4 address of the LPSM instance as its Server Alias.

Do not use the change-ip command to change LPSM’s IP addresses, gateway, and netmask. AWS environment does not allow these changes after launching the instances.

Director AMIs Commands

The following commands are exposed to the Director AMIs:

growpart

Use the growpart command to extend the partition of the root volume.

resize2fs

Use the resize2fs command to resize the ext4 file systems.

Before extending a file system containing valuable data, create a snapshot of the volume if you need to roll back your changes.

For other commands, see the Director Fabric Commands, LPSM Commands, and Director Console Commands guides.