Importing LogLogic EVA to AWS

Note: By default, LogLogic EVA for AWS is configured for DHCP, which is the recommended configuration when running LogLogic EVA in AWS. However, settings such as NTP server and time can be configured as applicable.

Prerequisites

Ensure that you meet the following requirements:

Download the TIB_logeva_<version>_aws_vm_vhd.zip archive and extract its contents: eva_aws_vm-vhd-<version>.vhd
Tip: To extract the contents of the AWS archive (.zip) package, the built-in extraction feature provided by the latest operating systems should work. You might face issues extracting the contents on some older operating systems.
For Windows 7 or other older operating systems, the file archiver application 7-Zip is recommended.
AWS Import/Export Tools: AWS Command Line Interface (AWS CLI). For more information, see the AWS documentation:
- VM Import/Export
- Importing a VM as an Image Using VM Import/Export
An AWS Identity and Access Management (IAM) role, with permissions in your IAM policy to use VM Import/Export for S3.
See Required Permissions for IAM Users in the AWS documentation.

Note: For more information on creating a service role and setting the required permissions, see article #000030469 on the TIBCO Support website.
AWS Security Group with at least the following ports allowed:
- All ICMP | ALL
- DNS | UDP | 53
- HTTP | TCP | 80
- HTTPS | TCP | 443
- HTTPS | TCP | 4443
- SSH | TCP | 22
  Note: Depending on the features used, additional ports might be required. For detailed information about these ports, such as protocol, interface, and process name, see Port Assignments in the TIBCO LogLogic® Log Management Intelligence Administration.
  To use log forwarding, you must disable source and destination checking on your LogLogic EVA network interfaces. See Changing the Source/Destination Checking in the AWS documentation.
An Amazon Virtual Private Cloud (Amazon VPC) defined with a private IP range.
See Private IPv4 Addresses and Internal DNS Hostnames in the AWS documentation.
A static private IPv4 address from the VPC range of your subnet for the primary IP:
See the Network Interfaces section under Launching an Instance in the AWS documentation.

Procedure

Upload the eva_aws_vm-<version>.vhd file to an S3 bucket. This can be done either via the AWS Web Console or via the AWS CLI using the aws s3 command. For example:
```
aws s3 cp eva_aws_vm-<version>.vhd s3://<s3bucketname>/eva_aws_vm-<version>.vhd
```

Using the AWS CLI, run the aws ec2 import-image command to import the vhd image to an AWS Amazon Machine Image (AMI).

aws ec2 import-image --cli-input-json "{  \"Description\": \"<DESCRIPTION>\", \"DiskContainers\": [ { \"Description\": \"First CLI task\", \"UserBucket\": { \"S3Bucket\": \"<S3BUCKETNAME>\", \"S3Key\" : \"<EVAIMAGENAME>\" } } ]}"

For example, using the following command:

>aws ec2 import-image --cli-input-json "{  \"Description\": \" LMI EVA IMAGE \", \"DiskContainers\": [ { \"Description\": \"First CLI task\", \"User Bucket\": { \"S3Bucket\": \" my-eva-bucket \", \"S3Key\" : \" eva_aws_vm-6.1.0.vhd \" } } ]}"

produces the following output:

{
    "Status": "active",
    "Description": "LMI EVA Image",
    "Progress": "2",
    "SnapshotDetails": [
        {
            "UserBucket": {
                "S3Bucket": "my-eva-bucket",
                "S3Key": "eva_aws_vm-6.1.0.vhd"
            },
            "DiskImageSize": 0.0
        }
    ],
    "StatusMessage": "pending",
    "ImportTaskId": "import-ami-fgs8pjvt"
}

Note down the value of ImportTaskId because it can be used with the aws ec2 describe-import-image-tasks command to check the process of the import.

aws ec2 describe-import-image-tasks --import-task-id <IMPORTTASKID>

For example, after running the following command:

> aws ec2 describe-import-image-tasks --import-task-id "import-ami-fgs8pjvt"

the following output is obtained:

{
    "ImportImageTasks": [
        {
            "Status": "active",
            "Description": "LMI EVA IMAGE",
            "Progress": "28",
            "SnapshotDetails": [
                {
                    "UserBucket": {
                        "S3Bucket": "my-eva-bucket",
                        "S3Key": "eva_aws_vm-6.1.0.vhd"
                    },
                    "DiskImageSize": 5633254400.0,
                    "Description": "First CLI task",
                    "Format": "VHD"
                }
            ],
            "StatusMessage": "converting",
            "ImportTaskId": "import-ami-fg3kce60"
        }
    ]
}

After the job completes, log in to the AWS console and view the completed import under EC2 > IMAGES > AMI.

Result

You can identify your new LogLogic EVA AMI by the AMI name, which must be the same as the value of ImportTaskId.

What to do next

Launch the LogLogic EVA instance using the LogLogic EVA AMI from the AWS GUI or AWS CLI. During this process, ensure that you either generate a new SSH key pair or select an existing one. This is required for connecting to your instance via SSH. See the procedure at Amazon EC2 Key Pairs in the AWS documentation.

Perform the following additional configurations as required:

(Optional) While deploying LogLogic EVA, if you selected a machine type that has multiple storage disks, or if you want to further expand the local storage after deployment, then you must enable the storage growth feature in LogLogic EVA. Otherwise, you can see and use only the primary disk through LogLogic EVA, and not the additional disks. Perform the steps at Expanding the Local Storage of LogLogic EVA.
Warning: You cannot detach the volume once it is attached to a LogLogic EVA instance; doing so makes the instance unresponsive and then you must launch a new LogLogic EVA instance.
(Optional) To connect LogLogic EVA to a large number of devices, perform the steps at Configuring LogLogic EVA for Large Number of Devices.

Contents